Obscurant emission to assist image formation to automate agricultural management and treatment

ABSTRACT

Various embodiments relate generally to computer vision and automation to autonomously identify and deliver for application a treatment to an object among other objects, data science and data analysis, including machine learning, deep learning, and other disciplines of computer-based artificial intelligence to facilitate identification and treatment of objects, and robotics and mobility technologies to navigate a delivery system, more specifically, to an agricultural delivery system configured to identify and apply, for example, an agricultural treatment to an identified agricultural object. In some examples, a method may include calculating an amount of light originating from a light source sensed at a location in which an agricultural object is interposed between the light source and an image capture device, causing emission of an obscurant, and directing the obscurant to a region interposed between the light source and the agricultural object.

FIELD

Various embodiments relate generally to computer software and systems,computer vision and automation to autonomously identify and deliver forapplication a specific treatment to an object among other objects, datascience and data analysis, including machine learning, deep learning,and other disciplines of computer-based artificial intelligence tofacilitate identification and treatment of objects, wired and wirelessnetwork communications, and robotics and mobility technologies tonavigate a delivery system, as well as vehicles including associatedmechanical, electrical and electronic hardware, among objects in ageographic boundary to apply any number of treatments to objects, and,more specifically, to an agricultural delivery system configured toidentify and apply, for example, an agricultural treatment to anidentified agricultural object.

BACKGROUND

Global human population growth is expanding at a rate projected to reach10 billion or more persons within the next 40 years, which, in turn,will concomitantly increase demands on producers of food. To supportsuch population growth, food producers, including farmers, need togenerate collectively an amount of food that is equivalent to an amountthat the entire human race, from the beginning of time, has consumed upto that point in time. Many obstacles and impediments, however, likelyneed to be overcome or resolved to feed future generations in asustainable manner. For example, changes to the Earth's climate andunpredictable weather patterns negatively impact maintenance orenhancements in crop yields. Furthermore, limited or shrinking amountsof arable land on which to farm reduces opportunities to grow crops ordedicate land for other food production purposes.

Increased scarcity and costs of resources to produce food affects mostfarmers in less developed countries, as well as smaller farmers indeveloped countries. For example, the costs of crops sold (“cost ofgoods sold,” or “COGS”) are likely to increase beyond a range 60% to 70%of revenue. Costs of producing food, such as crops, may include costsdue to labor, chemicals (e.g., fertilizer, pesticides, etc.), packaging,provenance tracking, and capital equipment (e.g., tractors, combines,and other farm implements), among other activities or resources. Laborcosts are expected to rise as the demand for agricultural laborincreases while fewer persons enter the agricultural workforce. Someagricultural workers are relocating to urban areas in numbers thatincrease scarcity of labor, thereby causing an average age of anagricultural worker to rise. Equipment costs, including tractors andsprayers, as well as other farm implements (e.g., combines, plows,spreaders, planters, etc.) may require relatively large expenses topurchase or lease, as well as to maintain, fuel, and operate.

Costs relating to chemical inputs are likely to rise, too. For instance,health-related and environmental concerns may limit amounts and/or typesof chemicals, such as certain pesticides, that can be used to producevegetables, fruits, and other agricultural products. Also, while someadvances in chemistries may be beneficial, these advanced chemistriesmay be unaffordable for most applications by smaller farms, or farms inunderdeveloped countries, thereby possibly depriving farmers of optimalmeans to produce food. Further, applications of some chemistries, suchas herbicides, pesticides, and fertilizers, on agricultural cropsrequire sprayers to disperse chemicals in very small liquid droplets(e.g., using boom sprayers, mist sprayers, etc.). Spray nozzlesgenerally have orifices or apertures oriented in a line substantiallyperpendicular to and facing the ground at a distance above the crops(relative to the soil), with the apertures designed to form overlappingflat fan or cone-shaped patterns of spray. Such conventional approachesto applying chemistries, however, usually results in amounts of sprayfalling upon non-intended targets, such as on the soil, which iswasteful.

The above-described costs likely contribute to increases in food pricesand farm closures, and such costs may further hinder advances to improvecrop yields to meet sufficiently the projected increases in humanpopulation. While functional, a few approaches to improve crop yieldshave been developed, and typically have a number of drawbacks. In sometraditional approaches, information to assist crop development relies onmulti-spectral imagery from satellites, aircraft, and/or drones.Multi-spectral imagery combined with location information, such asprovided by Global Positioning Systems (“GPS”), enables coarse analysisof portions of a farm to determine soil characteristics, fertilizerdeficiencies, topological variations, drainage issues, vegetation levels(e.g., chlorophyll content, absorption, reflection, etc.), and the like.Thus, multi-spectral may be used to identify various spectral, spatial,and temporal features with which to evaluate the status of a group ofcrops as well as changes over time. There are various drawbacks to relyon this approach. For example, data based on multi-spectral imagery aregenerally limited to coarse resolutions related to crop-relatedmanagement. That is, multi-spectral imagery generally providesinformation related to certain areas or region including multiple rowsof crops or specific acreage portions. Further, multi-spectral imageryis not well-suited for monitoring or analyzing botanical itemsgranularly over multiple seasons. In particular, such imagery may belimited to detectable foliage, for example, midway through a cropseason. Otherwise, multi-spectral imagery may be limited, at least insome cases, to a set of abiotic factors, such as the environmentalfactors in which a crop is grown, and, thus, may be insufficient toidentify a specific prescriptive action (e.g., applying fertilizer, aherbicide, etc.) for one or more individual plants that may not bedetectable using multi-spectral imagery techniques. As such,multi-spectral imagery may not be well-suited to analyze biotic factors,among other things.

In another traditional approach, known computer vision techniques havebeen applied to monitor agricultural issues at plant-level (e.g., as awhole plant, imaged from a top view generally). While functional, thereare a number of drawbacks to such an approach. For instance, somecomputer-based analyses have been adapted to perform agriculturalassessments with reliance on incumbent or legacy machinery and hardware,such as conventional tractors. The conventional tractors and other knownimplements are not well-suited to integrate with recent autonomoustechnologies to sufficiently navigate among crops to perform functionsor tasks less coarsely, or to identify and perform less coarse tasks ortreatments. For example, some conventional applications may vary ratesof dispensing fertilizer based on specific prescriptive maps that relyon resolutions provided by GPS and multi-spectral imagery (e.g.,satellite imagery). Hence, some conventional rates of applyingfertilizer are generally at coarse resolutions in terms of square meters(i.e., over multiple plants).

In some traditional approaches, known computer vision techniques aretypically implemented to identify whether vegetation is either anindividual crop or a non-crop vegetation (i.e., a weed). Further, thesetraditional approaches spray a chemical to generally treat a plantholistically, such as applying an herbicide to a weed or fertilizer to acrop. However, there is a variety of drawbacks to these traditionalapproaches. These approaches are typically directed to annual, row-basedcrops, such as lettuce, cotton, soybeans, cabbage, or other annualvegetation, which generally grow shorter than other vegetation.Row-based crops, also known as “row crops,” typically are crops tilledand harvested in row sizes relative to agricultural machinery, wherebyrow crops naturally are rotated annually to replace entire vegetativeentities (e.g., removal of corn stalks, etc.). Also, row-based crops aretypically planted in row widths of, for example, 15, 20, or 30 inch rowwidths, with conventional aims to drive row widths narrower to reduceweed competition and increase shading of the soil, among other things.

In some traditional approaches, known computer vision techniques appliedto row crops rely on capturing imagery of vegetation at a distance abovethe ground and oriented generally parallel to a direction of gravity(e.g., top-down). As such, the background of imagery is typically soil,which may simplify processes of detecting vegetation relative tonon-vegetation (e.g., the ground). Further, images captured by a cameramay have relatively minimal a depth of view, such as a distance from thesoil (e.g., as a farthest element) to the top of an individual crop,which may be a row crop. Row crops have relatively shorter depth of viewthan other vegetation, including trees or the like, or otherconfigurations. Known computer vision techniques have also been used, insome cases, to apply a fertilizer responsive to identifying anindividual plant. In these cases, fertilizer has been applied as aliquid, whereby the liquid is typically applied using streams ortrickles of liquid fertilizer. Further, the application of liquidfertilizer generally relies on a gravitational force to direct a streamof fertilizer to the individual crop.

Thus, what is needed is a solution for facilitating application of atreatment to an identified agricultural object, without the limitationsof conventional techniques.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments or examples (“examples”) of the invention aredisclosed in the following detailed description and the accompanyingdrawings:

FIG. 1A is a diagram depicting an example of an agricultural treatmentdelivery system, according to some embodiments;

FIG. 1B is a diagram depicting an example of an emitter configured toapply a treatment, according to some examples;

FIG. 2A is a diagram depicting examples of sensors and components of anagricultural treatment delivery vehicle, according to some examples;

FIG. 2B depicts generation of indexed agricultural object data,according to some embodiments;

FIG. 3 is an example of a flow diagram to control agricultural treatmentdelivery system autonomously, according to some embodiments;

FIG. 4 is a functional block diagram depicting a system including aprecision agricultural management platform communicatively coupled via acommunication layer to an agricultural treatment delivery vehicle,according to some examples;

FIG. 5 is a diagram depicting another example of an agriculturaltreatment delivery system, according some examples;

FIG. 6 is an example of a flow diagram to align an emitter to a targetautonomously, according to some embodiments;

FIGS. 7A and 7B depict examples of data generated to identify, track,and perform an action for one or more agricultural objects in anagricultural environment, according to some examples;

FIG. 7C is a diagram depicting parameters with which to determineactivation of an emitter to apply a treatment, according to someexamples;

FIG. 8 is a diagram depicting a perspective view of an agriculturalprojectile delivery vehicle configured to propel agriculturalprojectiles, according to some examples;

FIG. 9 is a diagram depicting an example of trajectory configurations tointercept targets autonomously using an agricultural projectile deliveryvehicle, according to some examples;

FIG. 10 is a diagram depicting examples of different emitterconfigurations of agricultural projectile delivery systems, according tosome examples;

FIG. 11 is a diagram depicting yet another example of an emitterconfiguration of an agricultural projectile delivery system, accordingto some examples;

FIGS. 12 and 13 are diagrams depicting examples of a trajectoryprocessor configured to activate emitters, according to some examples;

FIG. 14 is a diagram depicting an example of components of anagricultural projectile delivery system that may constitute a portion ofan emitter propulsion subsystem, according to some examples;

FIG. 15 is a diagram depicting an example of an arrangement of emittersoriented in one or more directions in space, according to some examples;

FIG. 16 is a diagram depicting an example of another arrangement ofemitters configured to be oriented in one or more directions in space,according to some examples;

FIG. 17 is a diagram depicting one or more examples of calibrating oneor more emitters of an agricultural projectile delivery system,according to some examples;

FIG. 18 is a diagram depicting another one or more examples ofcalibrating one or more emitters of an agricultural projectile deliverysystem, according to some examples;

FIG. 19 is an example of a flow diagram to calibrate one or moreemitters, according to some embodiments;

FIGS. 20 and 21 are diagrams depicting an example of calibratingtrajectories of agricultural projectiles in-situ, according to someexamples;

FIG. 22 is a diagram depicting deviations from one or more opticalsights to another one or more optical sights, according to someexamples;

FIG. 23 is a diagram depicting an agricultural projectile deliverysystem configured to implement one or more payload sources to providemultiple treatments to one or more agricultural objects, according tosome examples;

FIG. 24 is an example of a flow diagram to implement one or more subsetsof emitters to deliver multiple treatments to multiple subsets ofagricultural objects, according to some embodiments;

FIG. 25 is an example of a flow diagram to implement one or morecartridges as payload sources to deliver multiple treatments to multiplesubsets of agricultural objects, according to some embodiments;

FIGS. 26 to 31 are diagrams depicting components of an agriculturaltreatment delivery vehicle configured to sense, monitor, analyze, andtreat one or more agricultural objects of a fruit tree through one ormore stages of growth, according to some examples;

FIG. 32 is a diagram depicting an example of a flow to manage stages ofgrowth of a crop, according to some examples;

FIG. 33 is a diagram depicting an agricultural projectile deliveryvehicle implementing an obscurant emitter, according to some examples;

FIG. 34 is a diagram depicting an example of a flow to facilitateimaging a crop in an environment with backlight, according to someexamples;

FIG. 35 is a diagram depicting a pixel projectile delivery systemconfigured to replicate an image on a surface using pixel projectiles,according to some embodiments;

FIG. 36 is a diagram depicting an example of a pixel projectile deliverysystem, according to some examples;

FIG. 37 is a diagram depicting an example of a flow to implement a pixelprojectile delivery system, according to some examples; and

FIG. 38 illustrates examples of various computing platforms configuredto provide various functionalities to components of an autonomousagricultural treatment delivery vehicle and fleet service, according tovarious embodiments.

DETAILED DESCRIPTION

Various embodiments or examples may be implemented in numerous ways,including as a system, a process, an apparatus, a user interface, or aseries of program instructions on a computer readable medium such as acomputer readable storage medium or a computer network where the programinstructions are sent over optical, electronic, or wirelesscommunication links. In general, operations of disclosed processes maybe performed in an arbitrary order, unless otherwise provided in theclaims.

A detailed description of one or more examples is provided below alongwith accompanying figures. The detailed description is provided inconnection with such examples, but is not limited to any particularexample. The scope is limited only by the claims, and numerousalternatives, modifications, and equivalents thereof. Numerous specificdetails are set forth in the following description in order to provide athorough understanding. These details are provided for the purpose ofexample and the described techniques may be practiced according to theclaims without some or all of these specific details. For clarity,technical material that is known in the technical fields related to theexamples has not been described in detail to avoid unnecessarilyobscuring the description.

FIG. 1A is a diagram depicting an example of an agricultural treatmentdelivery system, according to some embodiments. Diagram 100 depicts anagricultural treatment delivery system configured to identify anagricultural object to apply an agricultural treatment. Examples of anagricultural treatment delivery system includes agricultural treatmentdelivery system 111 a and agricultural treatment delivery system 111 b,whereby agricultural treatment delivery systems 111 a and 111 b may beconfigured to deliver same or different treatments into an environmentin which agricultural objects may be present. Agricultural treatmentdelivery system 111 a may include one or more emitters, such as emitter112 c. Emitter 112 c may be configured emit a treatment 112 b, forexample, via a trajectory 112 d in any direction to intercept a target(“T”) 112 a as vehicle 110 traverses path portions 119 at a velocity, v.In some cases, vehicle 110 may be in a static position. A direction oftrajectory 112 d may be within a two- or three-dimensional spacedescribed relative to an XYZ coordinate system or the like. Examples oftarget 112 a may include a bud, blossom, or any other botanical oragricultural object likely to be sensed in an environment within ageographic boundary 120, which may include at least a portion of a farm,an orchard, or the like.

Agricultural treatment delivery system 111 a may be disposed in avehicle, such as vehicle 110, to facilitate mobility to any number oftargets 112 a within a geographic boundary 120 to apply a correspondingtreatment 112 b. In some examples, vehicle 110 may includefunctionalities and/or structures of any motorized vehicle, includingthose powered by electric motors or internal combustion engines. Forexample, vehicle 110 may include functionalities and/or structures of atruck, such as a pick-up truck (or any other truck), an all-terrainvehicle (“ATV”), a utility task vehicle (“UTV”), or any multipurposeoff-highway vehicle, including any agricultural vehicle, includingtractors or the like. Also, agricultural treatment delivery systems 111a and 112 b, as well as other agricultural treatment delivery systems(not shown), may be implemented in a trailer (or other mobile platform)that may be powered or pulled separately by a vehicle, which maynavigate path portions 119 manually or autonomously. As shown, vehicle110 may include a manual controller or control module (“cab”) 115, whichmay accommodate a human driver and include any mechanical controlsystem, such as a steering wheel and associated linkages to steerablewheels, as well as manually controlled braking and acceleratorsubsystems, among other subsystems.

In some examples, vehicle 110 may include a mobility platform 114 thatmay provide logic (e.g., software or hardware, or both), andfunctionality and/or structure (e.g., electrical, mechanical, chemical,etc.) to enable vehicle 110 to navigate autonomously over one or morepaths 119, based on, for example, one or more treatments to be appliedto one or more agricultural objects. Any of agricultural treatmentdelivery systems 111 a or 111 b may be configured to detect, identify,and treat agricultural objects autonomously (e.g., without manualintervention) independent of whether vehicle 110 is configured tonavigate and traverse path portions 119 either manually or autonomously.

In the example shown, agricultural treatment delivery system 111 may beconfigured to traverse path portions 119 adjacent to agriculturalobjects, such as trees, disposed in arrangements 122 a, 122 b, 122 c,122 d, and 122 n, or any other agricultural objects associatedtherewith. In some cases, arrangements 122 a, 122 b, 122 c, 122 d, and122 n may be any trellis-based structure, such as any espalier-supportedpattern or any trellis configuration (e.g., substantially perpendicularconfigurations, an example of which is shown in diagram 100, or“V-shaped” trellises, or any other structure). Note that agriculturaltreatment delivery system 111 need not be limited to trellis-basedstructures, but rather may be used with any plant or vegetativestructure.

Any of agricultural treatment delivery systems 111 a or 111 b may beconfigured to operate, for example, in a sensor mode during which asensor platform 113 may be configured to receive, generate, and/orderive sensor data from any number of sensors as vehicle 110 traversesvarious path portions 119. For example, sensor platform 113 may includeone or more image capture devices to identify and/or characterize anagricultural object, thereby generating. Examples of image capturedevices include cameras (e.g., at any spectrum, including infrared),Lidar sensors, and the like. Image-based sensor data may include anyinclude any data associated with an agricultural object, such as imagesand predicted images, that may describe, identify, or characterizephysical attributes. Sensor platform 113 may also include one or morelocation or position sensors, such as one or more global positioningsystem (“GPS”) sensors and one or more inertial measurement units(“IMU”), as well as one or more radar devices, one or more sonardevices, one or more ultrasonic sensors, one or more gyroscopes, one ormore accelerometers, one or more odometry sensors (e.g., wheel encoderor direction sensors, wheel speed sensors, etc.), and the like.Position-based sensors may provide any data configured to determinelocations of an agricultural object relative to a reference coordinatesystem, to vehicle 110, to emitter 112 c, or to any other object based,for example, GPS data, inertial measurement data, and odometry data,among data generated by other position and/or location-related sensors.

Note that any sensor or subset of sensors in sensor platform 113 may beconfigured to provide sensor data for any purpose. For example, anyimage capture device may be configured to detect a visual fiducialmarker or any other optically-configured item (e.g., a QS code, barcode,or the like) that may convey information, such as position or locationinformation, or other information. As agricultural treatment deliverysystem 111 and/or sensory platform 113 traverses path portions 119,image capture devices may detect fiducial markers, reflective surfaces,or the like, so that logic within sensory platform 113 or vehicle 110(e.g., one or more processors and one or more applications includingexecutable instructions) may be configured to detect or confirm aposition of vehicle 110 or emitter 112 c, or both, as a position withingeographic boundary 120 or relative to an agricultural object.

In some implementations, one or more sensors in sensor platform 113 maybe distributed among any portion of vehicle in any combination. Forexample, sensors in sensor platform 113 may be disposed in any ofagricultural treatment delivery systems 111 a or 111 b. As such, any ofagricultural treatment delivery systems 111 a or 111 b may each beconfigured to localize or determine a position of emitter 112 c relativeto an agricultural object independently. That is, agricultural treatmentdelivery systems 111 a or 111 b may include sensors and logic todetermine the position of an emitter 112 c in association with, orrelative to, an agricultural object, and may be configured to identifyan agricultural object autonomously, orient or otherwise target thatagricultural object for action autonomously, and/or perform an action orapply a treatment autonomously regardless of whether vehicle 110 isnavigating manually or autonomously.

One or more of agricultural treatment delivery systems 111 a and 111 bmay be implemented as a modular structure that may be loaded into a bedof a pickup truck or an ATV/UTV, or any other vehicle that may beconfigured to manually navigate agricultural treatment delivery system111 along path portions 119 to sense an agricultural object and toperform an action therewith. In some implementations, one or moresensors in sensor platform 113 may be distributed among any portion ofvehicle, for example, including mobility platform 114, to facilitateautonomous navigation, agricultural object identification, and performan action (e.g., apply a treatment). Hence, agricultural treatmentdelivery system 111 may implement sensors or sensor data (e.g.,individually or collectively), or may share or use sensors and sensordata used in association with mobility platform 114 to facilitateautonomous navigation of vehicle 110. In one example, sensor platform113 may be disposed in mobility platform 114, or in or among any otherportion. Mobility platform 114 may include hardware or software, or anycombination thereof, to enable vehicle 110 to operate autonomously.

Sensor platform 113 may be configured to sense, detect, analyze, store,and/or communicate data associated with one or more agriculturalobjects. For example, sensor platform 113 may be configured to at leastdetect or sense a subset 123 b of one or more agricultural objectsassociated with tree 121 a positioned adjacent path portion 119 a.Sensor platform 113 also may be configured to detect subset 123 b ofagricultural objects as, for example, a limb, a branch, or any portionof agricultural object (“tree”) 121 a, and may further detect othersub-classes of agricultural objects of subset 123 b. Sub-classes ofagricultural objects of subset 123 b may include buds, such as growthbuds 125 (e.g., a bud from which a leaf or shoot may develop) and fruitbuds 124 and 126, each of which may be an agricultural object. Branch123 a may also include a limb 127 as an agricultural object, and mayinclude other agricultural objects, such as a spur (e.g., a shoot thatmay develop fruit), a water sprout (e.g., a young shoot growing withintree 121 a), and the like.

In some embodiments, agricultural treatment delivery system 111 may beconfigured to communicate agricultural object data 197 via anycommunication media, such as wireless radio transmissions, to aprecision agricultural management platform 101. Precision agriculturalmanagement platform 101 may include hardware (e.g., processors, memorydevices, etc.) or software (e.g., applications or other executableinstructions to facilitate machine learning, deep learning, computervision techniques, statistical computations, and other algorithms), orany combination thereof. Precision agricultural management platform 101(or portions thereof) may reside at any geographic location, whether ator external to geographic location 120. In one or more examples, logicassociated with either precision agricultural management platform 101 oragricultural treatment delivery system 111, or both, may be configuredto implement or facilitate implementation of simultaneous localizationand mapping (“SLAM”) to support autonomous navigation of vehicle 110, aswell as autonomous operation of agricultural treatment delivery systems111 a and 111 b. Hence, agricultural treatment delivery systems 111 aand 111 b may implement SLAM, or any other technique, to apply atreatment to an agricultural object autonomously.

Precision agricultural management platform 101 may be configured to,index and assign a uniquely identifier to each agricultural object intransmitted data 197 (e.g., as a function of a type of agriculturalobject, such as a blossom, a location of the agricultural object, etc.).Precision agricultural management platform 101 also may operate to storeand manage each agricultural object (in agricultural object data 197) asindexed agricultural object data 102 a, whereby each data arrangementrepresenting each indexed agricultural object may be accessed using anidentifier.

In some cases, either precision agricultural management platform 101 oragricultural treatment delivery system 111, or both, may be configuredto implement computer vision and machine learning algorithms toconstruct and maintain a spatial semantic model (e.g., at resolutions ofsub-centimeter, or less) and/or a time-series model of plant physiologyand state-of-growth. Data representing any of these models may bedisposed in data representing indexed agricultural object data 102 a.For example, agricultural treatment delivery system 111 may beconfigured to navigate path portions 119 at any time in autumn, winter,spring, and summer to monitor a status of tree 121 a and associatedsubsets of agricultural objects. For example, sensor platform 113 and/oragricultural treatment delivery system 111 may capture sensor dataassociated with fruit bud 126, which may develop over time throughprogressive stages of growth. At stage 130, fruit bud 126 is shown in an“open cluster” stage with flower buds 131 being, for example, pink incolor and prior to blossom. The open cluster stage is indicated at time,T, equivalent to t(OC), with “OC” referring to “open cluster.” At stage132, the open cluster may transition over time (and through otherintermediate stages, which are not shown) into a “blossom” stage inwhich a first (e.g., King) blossom 133 opens. The blossom stage isindicated at time, T, equivalent to t(1^(st) BL), with “BL” referring to“blossom.” At stage 133, the blossom stage may transition over time (andthrough other intermediate stages, which are not shown) into a “fruit”stage in which a first blossom ripens into a fruit 135. The fruit stageis indicated at time, T, equivalent to t(opt), with “opt” referring toan optimal time at which fruit 135 may be optimally ripened for harvest.

Continuing with the example of detecting various stages in the growth ofa crop, sensor platform 113 may transmit sensor data as agriculturalobject data 197 to precision agricultural management platform 101, whichmay analyze sensor data representing one of stages 130, 132, and 134 todetermine an action to be performed for a corresponding stage. Forexample, at stage 132, logic in precision agricultural managementplatform 101 may be configured to identify at least one action to beperformed in association with blossom 133. An action may includeapplying a treatment to blossom 133, such as causing emitter 112 c toapply treatment 112 b to blossom 133 as target 112 a. The treatment mayinclude applying pollen to, for example, a stigma of blossom 133 toeffect germination. In various examples, precision agriculturalmanagement platform 101 may be configured to generate and store policydata 102 b in repository 102, and be further configured to transmitpolicy and/or index data 195 to agricultural treatment delivery system111 a.

Any of agricultural treatment delivery systems 111 a or 111 b may beconfigured to operate, for example, in an action mode during which asensor platform 113 may be configured to receive policy data 195associated with blossom 133, which may be uniquely identifiable as anindexed agricultural object. Policy data may specify that blossom 133 isto be pollenated. Sensor platform 113 may be configured further toreceive and/or generate sensor data from any number of sensors asvehicle 110 traverses various path portions 119, the sensor data beingconfigured to identify an image of blossom 133 as vehicle traverses pathportion 119 a. When sensor platform 113 detects blossom 133,agricultural treatment delivery system 111 a may be configured totrigger emission of treatment 112 b autonomously. Note that agriculturaltreatment delivery systems 111 a or 111 b each may operate in sensor andaction modes, individually or simultaneously, and may operate in anynumber of modes. Each mode may be implemented individually orcollectively with any other mode of operation.

In some examples, agricultural treatment delivery systems 111 andvehicle 110 may operate to provide “robotics-as-a-service,” and inparticular, “robotics-as-an-agricultural-service” to enhance automationof crop load management and yield enhancement at least an agriculturalobject basis (or at finer resolution). For example, an apple crop may bemonitored (e.g., during each pass of vehicle 110) and treated withmicro-precision, such as on a per-cluster basis or a per-blossom basis.Vehicle 110 and other equivalent vehicles 199 may constitute a fleet ofautonomous agricultural vehicles 110, each of which may identifyagricultural objects and apply corresponding treatments autonomously. Inat least one example, vehicle 110 may be configured to traverse, forexample, 50 acres (or more) at least two times each day to generate andmonitor sensor data, as well as to apply various treatments. In somecases, a computing device 109 may be configured to receive sensor data(e.g., image data) and to transmit executable instructions to perform aremote operation (e.g., a teleoperation) under guidance of user 108, whomay be an agronomist or any other user including data analysts,engineers, farmers, and the like. Computing device 109 may provideremote operation to either navigate vehicle 110 or apply a treatment 112b via emitter 112 c, or both.

FIG. 1B is a diagram depicting an example of an emitter configured toapply a treatment, according to some examples. Diagram 150 includes anemitter 152 c that may be configured to apply treatments to agriculturalobjects, such as one or more portions of agricultural object depicted asa blossom. An agricultural treatment delivery system may be configuredto apply units (e.g., distinct units) of treatment that may include, forexample, packetized portions of a fertilizer, a thinning chemical, anherbicide, a pesticide, or any other applicable agricultural material orsubstance. As shown, emitter 152 c may be configured to apply atreatment with micro-precision by emitting an agricultural projectile152 b to intercept a target 152 ab at or within a target dimension 151.For example, target dimension 151 may have a dimension (e.g., adiameter) of 1 centimeter (“cm”) or less. Hence, emitter 152 c maydeliver a treatment with a micro-precision of, for example, 1 cm orless, at any trajectory angle.

Agricultural projectile 152 b may be configured as a liquid-basedprojectile propelled from emitter 152 c for a programmable interval oftime to form the projectile having, for example, an envelope 156 b, atleast in one example. Emitter 152 c may be configured to emitagricultural projectile 152 b along a trajectory direction 155 a, whichmay be any direction in two or three-dimensional space. In at least oneexample, emitter 152 c may be configured to propel agriculturalprojectile 152 b in trajectory direction 155 a with a force having avertical component (“Fvc”) and a horizontal component (“Fhc”). As shown,the vertical component of the propulsion force may be in a directionopposite than the force of gravity (“Fg”). Note, however, any ofvertical component (“Fvc”) and a horizontal component (“Fhc”) may benegligible or zero, at least in one implementation. Note, too, thathorizontal component (“Fhc”) may have a magnitude sufficient to propelagricultural projectile 152 b over a trajectory distance 154. Intreatments applied to, for example, trellis or orchard crops, trajectorydistance 154 may be 3 meters or less. In treatments applied to, forexample, row crops, trajectory distance 154 may be 1 meter or less. Inat least one example, trajectory distance 154 may be any distance withina geographic boundary.

In at least one other example, emitter 152 c may be configured to emitagricultural projectile 152 b along trajectory direction 155 a in anenvelope 156 a to intercept a target 152 aa having a target dimension153. As an example, target dimension 153 may have a dimension (e.g., adiameter) equivalent to a size of an apple (or a size equivalent to anyother agricultural object). Thus, emitter 152 c may be configured tomodify a rate of dispersal with which portions of agriculturalprojectile 152 b disperses at or about a range of a target of aparticular size. According to some examples, trajectory direction 155 amay be coaxial with an optical ray extending, for example, from at leastone of a first subset of pixels of an image capture device to at leastone pixel of a second subset of pixels including an image of target 152ab. Further, one or more of the first subset of pixels may be configuredas an optical sight. Thus, when at least one pixel of the optical sightaligns with at least one pixel of the target image, an agriculturalprojectile may be propelled to intercept target 152 ab. In someexamples, emitter 152 c may include an aperture that is alignedcoaxially with the optical ray. An example of emitter 152 c includes anozzle. According to at least one implementation, disposing andorienting emitter 152 coaxially to an optical ray facilitates, forexample, two-dimensional targeting. Therefore, a range or distance oftarget 152 b may be positioned anywhere, such as at points A, B, or C,along the optical ray and may be intercepted without calculating orconfirming an actual or estimated distance or three-dimensionalposition, at least in some examples.

In some examples, a dosage or amount of treatment (e.g., fertilizer) maybe applied at variable amounts by, for example, slowing a speed ofvehicle and extending an interval during which agricultural projectile152 b is propelled or emitted. In at least one case, an amount ofpropulsion (e.g., a value of pressure of a propellant, such as acompressed gas) may be modified as a function of trajectory distance 154or any other factor, such as an amount of wind. In some cases, multipleagricultural projectile 152 b of the same or different amounts may bepropelled to intercept a common target 152 a. Agricultural projectile152 b may include an inert liquid to increase viscosity, which mayreduce a rate of dispersal, at least in some implementations. In somecases, emitter 152 c can be configured to emit agricultural projectile152 b having a liquid configured to be emitted with a laminar flowcharacteristics (e.g., with minimal or negligible turbulent flowcharacteristics). According to other examples, an emitter need not alignwith an optical ray and may use multiple image devices to orientalignment of an emitter to a target independently of an optical rayassociated with an in-line camera.

FIG. 2A is a diagram depicting examples of sensors and components of anagricultural treatment delivery vehicle, according to some examples.Diagram 200 depicts expanded component view of an agricultural treatmentdelivery vehicle 210 that may provide a mechanical and electricalstructure, such as structures implemented in pick-up tracks, flatbedtrucks, ATVs, UTVs, tractors, and the like. Agricultural treatmentdelivery vehicle 210 may include a power plant, such as an internalcombustion engine or an electric battery-powered motor. As shown,agricultural treatment delivery vehicle 210 may include a sensorplatform 213 including any number and type of sensor, whereby any sensormay be located and oriented anywhere on agricultural treatment deliveryvehicle 210. For example, sensors depicted in diagram 200 may beimplemented as sensor platform 213 (or a portion thereof). Sensors inFIG. 2A include one or more image capture sensors 236 (e.g., lightcapture devices or cameras of any type, including infrared camera toperform action at night or without sunlight), one or more radar devices237, one or more sonar devices 238 (or other like sensors, includingultrasonic sensors or acoustic-related sensors), and one or more Lidardevices 234, among other sensor types and modalities (some of which maynot be shown, such as inertial measurement units, or “IMUS,” globalpositioning system (“GPS”) sensors, temperature sensors, soilcomposition sensors, humidity sensors, barometric pressure sensors,light sensors, etc.). In some cases, sensor platform 213 may alsoinclude an airflow direction sensor 201 (e.g., wind direction) and/or anairflow speed sensor 202 (e.g., wind speed), where the direction andspeed of air flow may be relative to a direction and velocity ofagricultural treatment delivery vehicle 210.

Agricultural treatment delivery vehicle 210 may include an agriculturaltreatment delivery system 211 including any number of emitters 212, eachof which may be oriented to propel an agricultural projectile at anydirection from a corresponding emitter. In some examples, each emitter212 may be oriented to propel an agricultural projectile via atrajectory that may be coaxial to an optical ray associated with aportion of a digitized image of an agricultural environment thatincludes one or more crops, or agriculture objects.

Further, agricultural treatment delivery vehicle 210 may include amotion estimator/localizer 219 configured to perform one or morepositioning and localization functions. In at least one example, motionestimator/localizer 219 may be configured to determine a location of oneor more component of agricultural treatment delivery vehicle 210relative to a reference coordinate system that may facilitateidentifying a location at specific coordinates (i.e., within a geometricboundary, such as an orchard or farm). For example, motionestimator/localizer 219 may compute a position of agricultural treatmentdelivery vehicle 210 relative to a point associated with vehicle 210(e.g., a point coincident with a center of mass, a centroid, or anyother point of vehicle 210). As another example, a position ofagricultural treatment delivery system 211 or any emitter 212 may bedetermined relative to a reference coordinate system, or relative to anyother reference point, such as relative to a position of agriculturaltreatment delivery vehicle 210. In yet another example, a position of anagricultural object may be determined using sensors in platform 213 andmotion estimator/localizer 219 to calculate, for example, a relativeposition of an agricultural object relative to a position of emitter 212to facilitate identification of an indexed agricultural object (e.g.,using image sensors data) and to enhance accuracy and precision ofdelivering an agricultural project to a target. According to someembodiments, data describing a position may include one or more of anx-coordinate, a y-coordinate, a z-coordinate (or any coordinate of anycoordinate system), a yaw value, a roll value, a pitch value (e.g., anangle value), a rate (e.g., velocity), altitude, and the like.

In some examples, motion estimator/localizer 219 may be configured toreceive sensor data from one or more sources, such as GPS data, wheeldata (e.g., odometry data, such as wheel-related data including steeringangles, angular velocity, etc.), IMU data, Lidar data, camera data,radar data, and the like, as well as reference data (e.g., 2D map dataand route data). Motion estimator/localizer 219 may integrate (e.g.,fuse the sensor data) and analyze the data by comparing sensor data tomap data to determine a local position of agricultural treatmentdelivery vehicle 210 or emitter 212 relative to an agricultural objectas a target, or relative to a waypoint (e.g., a fiducial marker affixedadjacent a path). According to some examples, motion estimator/localizer219 may generate or update position data in real-time or near real-time.

Agricultural treatment delivery vehicle 210 may include a mobilitycontroller 214 configured to perform one or more operations tofacilitate autonomous navigation of agricultural treatment deliveryvehicle 210. For example, mobility controller 214 may include hardware,software, or any combination thereof, to implement a perception engine(not shown) to facilitate classification of objects in accordance with atype of classification, which may be associated with semanticinformation, including a label. A perception engine may classify objectsfor purposes of navigation (e.g., identifying a path, other vehicles,trellis structures, etc.), as well as for purposes of identifyingagricultural objects to which a treatment may be applied. For example, aperception engine may classify an agricultural object as a bud, ablossom, a branch, a spur, a tree, a cluster, a fruit, etc. Mobilitycontroller 214 may include hardware, software, or any combinationthereof, to implement a planner (not shown) to facilitate generation andevaluation of a subset of vehicle trajectories based on at least alocation of agricultural treatment delivery vehicle 210 against relativelocations of external dynamic and static objects. The planner may selectan optimal trajectory based on a variety of criteria over which todirect agricultural treatment delivery vehicle 210 in way that providesfor collision-free travel or to optimize delivery of an agriculturalprojectile to a target. In some examples, a planner may be configured tocalculate the trajectories as probabilistically-determined trajectories.Mobility controller 214 may include hardware, software, or anycombination thereof, to implement a motion controller (not shown) tofacilitate conversion any of the commands (e.g., generated by theplanner), such as a steering command, a throttle or propulsion command,and a braking command, into control signals (e.g., for application toactuators, linkages, or other mechanical interfaces 217) to implementchanges in steering or wheel angles and/or velocity autonomously.

In some examples, agricultural treatment delivery system 211, sensorplatform 213 (including any sensor), and motion estimator/localizer 219may be implemented as a modular agricultural treatment delivery system221, which can be configured to autonomously identify agriculturalobjects and apply a treatment to each agricultural object in accordancewith a policy (e.g., application of a certain treatment responsive tostage of growth, and environmental condition, biotic data, abiotic data,etc.). Therefore, modular agricultural treatment delivery system 221 maybe disposed in a truck, ATV, tractor, etc., any of which may benavigated manually (e.g., by a human driver) using manual control order215. In some example, agricultural treatment delivery system 211 mayhave logic, similar or equivalent to that in mobility controller 214.For instance, agricultural treatment delivery system 211 may beconfigured to implement one or more of a perception engine to detect andclassify agricultural objects, a planner to determine actions (e.g., oneor more trajectories over which to propel an agricultural projectile),and a motion controller to control, for example, position or orientationof emitter 212. In other examples, agricultural treatment deliverysystem 211, sensor platform 213 (including any sensor), and motionestimator/localizer 219 each may integrated into a modular agriculturaltreatment delivery system 221, which, in turn, may be integrated intoagricultural treatment delivery vehicle 210, along with mobilitycontroller 214, to facilitate autonomous navigation of vehicle 210 andautonomous operation of agricultural treatment delivery system 211.

While agricultural treatment delivery vehicle 210 is described forapplications in agriculture, delivery vehicle 210 need not be solimiting and may be implemented in any other type of vehicle, whether onland, in air, or at sea. Further, any agricultural projectile describedherein, need not be limited to liquid-based projectiles, and may includesolid and gas-based emissions or projectiles. Moreover, agriculturaltreatment delivery vehicle 210 need not be limited to agriculture, butmay be adapted for any of a number of non-agricultural applications.Also, agricultural treatment delivery vehicle 210 may be configured tocommunicate with a fleet 299 of equivalent delivery vehicles tocoordinate performance of one or more policies for any geographicboundary.

FIG. 2B depicts generation of indexed agricultural object data,according to some embodiments. Diagram 250 depicts an agriculturaltreatment delivery system 211, which, in turn, may optionally include asensor platform 213 and a motion estimator/localizer 219, according tosome examples. While sensor platform 213 is shown to include motionestimator/localizer 219, each may be separate or distributed over anynumber of structures (as well as constituent components thereof).Diagram 250 also depicts a precision agricultural management platform201 configured to receive agricultural object data 251 from agriculturaltreatment delivery system 211, and further configured to generateindexed agricultural object data 252 a, which may be stored in a datarepository 252. Note that elements depicted in diagram 250 of FIG. 2Bmay include structures and/or functions as similarly-named elementsdescribed in connection to one or more other drawings.

Agricultural object data 251 may include data associated with anon-indexed agricultural object, an updated agricultural object, or anyother information about an agricultural object. In some instances, anon-indexed agricultural object may be an agricultural object detectedat sensor platform 213, and may yet to be identified in, or indexedinto, a database of indexed agricultural object data 252 a. Precisionagricultural management platform 201 may be configured to identifyagricultural object data 251 as “non-indexed,” and may activateexecutable instructions to invoke indexing logic 253 to generate indexedagricultural object data 252 a based on agricultural object data 251,whereby indexed identifier data 254 (e.g., a unique identifier) may beassociated with agricultural object data 251. Also, agricultural objectdata 251 may include data associated with an updated agriculturalobject, such as when an agricultural object identified as being in a budstate at one point in time transitions to a blossom state (or any otherintermediate states) at another point in time. In this case,agricultural object data 251 may also include image data (e.g., datarepresenting a blossom) as well as any other sensor-based or deriveddata associated therewith, including an identifier (e.g., previouslydetermined).

In various examples, precision agricultural management platform 201 maybe configured to determine for agricultural object data 251 any otherassociated data provided or derived by, for example, sensors in sensorplatform 213 and motion estimator/localizer 219. For example, precisionagricultural management platform 201 may be configured to generate oneor more of location data 255, botanical object data 260 (e.g.,crop-centric data), biotic object data 272, abiotic object data 274,predicted data 282, action data 290, as well as any other dataassociated with agricultural object data 251, including agriculturalobject characteristics, attributes, anomalies, associated activities,environmental factors, ecosystem-related items and issues, conditions,etc. Any one or more of location data 255, botanical object data 260(e.g., crop-centric data), biotic object data 272, abiotic object data274, predicted data 282, and action data 290 may be included or omitted,in any combination.

Precision agricultural management platform 201 may be configured toidentify a location (e.g., a spatial location relative to atwo-dimensional or three-dimensional coordinate system) of anagricultural object associated with agricultural object data 251, thelocation being represented by geographic location data 255 a. In somecases, geographic location data 255 a may include a geographiccoordinate relative to a geographic boundary, such as a boundary of anorchard or farm. Geographic location data 255 a may include GPS datarepresenting a geographic location, or any other location-related data(e.g., derived from position-related data associated with a sensor,vehicle, or agricultural treatment delivery system). Location data 255may also include positioning data 255 b that may include one or moresubsets of data that may be used to determine or approximate a spatiallocation of the agricultural object associated with agricultural objectdata 251. For example, position data for one or more optical markers(e.g., reflective tape, visual fiduciary markers, etc.) may be includedin positioning data 255 b to locate or validate a spatial location foragricultural object data 251.

Botanical object data 260 may include any data associated with a plant,such as a crop (e.g., a specifically cultivated plant). For example,botanical object data 260 may include growth bud-related data 260, fruitbud-related data set 262, limb data 264, and trunk/stem data 266, andinclude other sub-classification of agricultural objects. Growthbud-related data 260 may include status data 261 a that may identify abud as being in a “bud state” at one point in time, which may bedetermined (at another point in time) to be in another state when thebud develops into either one or more leaves or a shoot. Physical data261 b may describe any attribute or characteristic of an agriculturalobject originating as a bud and that develops into one or more leaves ora shoot. For example, physical data 261 b may include a shape, color,orientation, anomaly, or the like, including image data, or anycharacteristic that may be associated with a leaf as an agriculturalobject.

Fruit bud-related data set 262 may include status data 262 a that mayidentify a fruit bud as being in a “fruit bud state” at one point intime, which may be determined (at another point in time) to be inanother state when the bud develops into, for example, one or moreblossoms as well as one or more fruit, such as one or more apples. Forexample, status data 262 a may include a subset of data 264 a to 264 kto describe a status or a state of growth associated with a fruit bud.The following description of sets of data 264 a to 264 k areillustrative regarding stages of growth of apples, and is not intendedto be limiting and can be modified for any fruit crop, vegetable crop,or any plant-related stages of growth, including ornamental plants, suchas flowers (e.g., roses), and the like.

Dormant data 264 a may include data associated with an identifieddormant fruit bud, including image data acquired or otherwise sensed atone or more points in time as physical data 262 b. Silver tip data 264 bmay include data associated with a stage of growth relative to a fruitbud transitioning to a “silver tip” stage of growth, including one ormore images thereof as physical data 262 b. In this stage, image datadepicting a fruit bud may include digitized images of scales that may beseparated at the tip of the bud, thereby exposing light gray or silvertissue. Green tip data 264 c may include data associated with a stage ofgrowth relative to a fruit bud transitioning to a “green tip” stage ofgrowth, including one or more images thereof as physical data 262 b. Inthis stage, a fruit bud may have developed to include image datadepicting a broken tip at which green tissue may be visible. Half-inchgreen data 264 d may include data associated with a stage of growthrelative to a fruit bud transitioning to a “half-inch” stage of growth,including one or more images thereof as physical data 262 b. At thisstage, a fruit bud may have developed to include image data depicting abroken tip at which approximately one-half inch of green tissue may bedetectable in an image. Tight cluster data 264 e may include dataassociated with a stage of growth relative to a fruit bud transitioningto a “tight cluster” stage of growth, including one or more imagesthereof as physical data 262 b. At this stage, a fruit bud may havedeveloped to include image data depicting a subset of blossom buds atvarious levels of visibility that may be detectable in an image, theblossom buds being tightly grouped.

Pink/pre-blossom data 264 f may include data associated with a stage ofgrowth relative to an initial fruit bud transitioning to a “pink” stageof growth (also known as “first pink,” “pre-pink,” or “full pink”stages) as well as (or up to) an “open cluster” stage, and one or moreimages thereof may be included in physical data 262 b. At this stage,image data may depict a subset of blossom buds at various levels of pinkcolors that may be detectable in an image prior to blossom. Blossom data264 g may include data associated with a stage of growth relative to aninitial fruit bud that may transition to a “blossom” stage of growth(also known as a “king bloom” or “king blossom” stage), and one or moreimages thereof may be included in physical data 262 b. At this stage,image data may depict a subset of pink blossom buds that include atleast one blossom, such as a “king blossom,” in an image.

Multi-blossom data 264 h may include data associated with a stage ofgrowth relative to a “multi-blossom” stage of growth (also known as a“full bloom” stage). One or more images of an agricultural object in a“multi-blossom” stage of growth may be included in associated physicaldata 262 b. At this stage, image data may depict a number of blossoms(e.g., after pink blossom buds bloom). Petal fall data 264 j may includedata based on a transition from a “multi-blossom” stage to a “petalfall” stage of growth. One or more images of an agricultural object in a“petal fall” stage of growth may be included in associated physical data262 b. At this stage, image data may depict a cluster of blossoms thathave a threshold amount of lost petals (e.g., 60% to 80% fallen) thathave detached from a central structure in an image. Fruit 264 k mayinclude data based on transitioning from a “petal fall” stage to a“fruit” stage of growth (also known as a “fruit set” stage). One or moreimages of an agricultural object in a “fruit” stage of growth may beincluded in associated physical data 262 b. At this stage, image datamay depict a number of fruit (e.g., one or more apples relative to acluster).

Limb data 264 may include status data 264 a that may identify orclassify a limb (e.g., a branch, a shoot, etc.) as being in a particularstate at one point in time, which may be determined (at another point intime) to be in another state when the limb develops and grows. Forexample, limb data 264 can include data specifying a limb as being in a“non-supportive” state (i.e., the limb size and structure may beidentified as being less likely to support growth of one or more applesto harvest). In this state, an agricultural treatment delivery systemmay be configured to apply a treatment, such as a growth hormone, topromote growth of the limb into, for example, a “supportive” state tofacilitate growth of apples. Physical data 264 b may describe anyattribute or characteristic of an agricultural object identified as alimb. For example, physical data 264 b may include a shape, size, color,orientation, anomaly, or the like, including image data, or anycharacteristic that may be associated with a limb as an agriculturalobject. Similarly, trunk/stem data 266 may include status data 266 athat may identify or classify a truck or a stem (or a portion thereof)as being in a particular state at a point in time, whereas physical data266 b may describe any attribute or characteristic of an agriculturalobject identified as a trunk or stem (or a portion thereof). Forexample, physical data 266 b may include a shape, size, dimensions,color, orientation, anomaly, or the like, including image data, or anycharacteristic that may be associated with a trunk or a stem as anagricultural object.

Biotic object data 272 may describe a living organism present in anecosystem or a location in a geographic boundary. For example, bioticobject data 272 may include status data 272 a that may identify a typeof bacteria, a type of fungi (e.g., apple scab fungus), a plant (e.g., anon-crop plant, such as a weed), and an animal (e.g., an insect, arodent, a bird, etc.), and other biotic factors that may influence oraffect growth and harvest of a crop. Status data 272 a may also identifydescribe any attribute or characteristic of a biotic object. Positioningdata 272 b may include data describing whether a biotic object ispositioned relative to, or independent from, another agricultural object(e.g., apple scab fungus may be identified as being positioned on anapple, which is another agricultural object). Positioning data 272 b maybe configured to locate or validate a spatial location of a bioticobject as agricultural object data 251.

Abiotic object data 274 may describe a non-living element (e.g., acondition, an environmental factor, a physical element, a chemicalelement, etc.) associated with an ecosystem or a location in ageographic boundary that may influence or affect growth and harvest of acrop. For example, abiotic object data 274 may include status data 274 athat may identify soil constituents (e.g., pH levels, elements, andchemicals), a time of day when abiotic data is sensed, amounts,intensities, directions of light, types of light (e.g., visible,ultraviolet, and infrared light, etc.), temperature, humidity levels,atmospheric pressure levels, wind speeds and direction, amounts of wateror precipitation, etc. Positioning data 272 b may include datadescribing whether an abiotic object is associated with anotheragricultural object, or any other data configured to locate or validatea spatial location of an abiotic object, such as portion of soil thatmay be acidic. Further, agricultural object data 251 may include anyother data 280, which may include any other status data 280 a and/or anyother supplemental data 280 b.

Further to FIG. 2B, precision agricultural management platform 201 mayinclude analyzer logic 203 and a policy generator 205. Analyzer logic203 may be configured to implement computer vision algorithms andmachine learning algorithms (or any other artificialintelligence-related techniques), as well as statistical techniques, toconstruct and maintain a spatial semantic model as well as a time-seriesmodel of physiology and/or physical characteristics of a crop (or anyother agricultural object, such as a limb or branch) relative to astage-of-growth. Analyzer logic 203 may be further configured to predicta next state or stage of growth and an associated timing (e.g., a pointin time or a range of time) at which a transition may be predicted.Hence, analyzer logic 203 may be configured to generate predicted data282 that may include predicted status data 282 a to describe a predictedstatus of an agricultural object associated with indexed identifier data254. For example, a predicted status of a cluster of blossoms, as anagricultural object, may specify a predicted transition from a singleopened blossom (e.g., a king blossom as an agricultural object) to oneor more lateral blossoms opening (e.g., as corresponding agriculturalobjects), as well as a predicted range of time during which thepredicted state transition may (likely) occur. Predicted data 282 mayinclude predicted image data 282 b that may be provided or transmittedto agricultural treatment delivery system 211 to facilitate detectingand identifying an agricultural object. Predicted image data 282 b maybe used to determine whether it may have transitioned from one state tothe next (e.g., since previously being sensed or monitored). Further,predicted data 282 may include predicted action data 282 c and any otherpredicted data 282 d, which may facilitate navigation and positioning ofan emitter to apply a treatment optimally (e.g., emitting anagricultural projectile within a range of accuracy and/or a range ofprecision), for example, as a function of context (e.g., season, stageof growth, associated biotic and abiotic conditions, time of day, amountof sunlight, etc.).

In some examples, policy generator 205 may be configured to analyze astatus (e.g., a current or last sensed status) of an agricultural objectand a predicted status, and may be further configured to derive one ormore actions as action data 290 as a policy. Action data 290 may beimplemented as policy data that is configured to guide performance ofone or more treatments to an agricultural object. For example, actiondata 290 associated with an agricultural object identified as a kingblossom may include data representing a policy (e.g., a definition,rules, or executable instructions) to perform an action (e.g., pollinatea king blossom), whereas action data 290 associated with an agriculturalobject identified as a lateral blossom (e.g., in association with acluster including a king blossom) may include policy data to perform athinning action to terminate growth of the lateral blossom. Action data290 may also include data representing prior actions performed as wellas results based on those prior actions, as well as any otheraction-related data.

FIG. 3 is an example of a flow diagram to control agricultural treatmentdelivery system autonomously, according to some embodiments. At 302,flow 300 begins to receive data configured to implement a policy toperform an action in association with an agricultural object. In somecases, data representing one or more actions to be performed relative toa subset of agricultural objects may be received at, for example, anagricultural treatment delivery system. Policy data may be configured toimplement an action based on a context associated with an agriculturalobject, such as a stage of growth during which, for example, pests andweeds may be more prominent than in other time intervals.

At 304, data representing a subset of agricultural objects may bereceived. In some cases, each agricultural object may be associated withdata representing an identifier. The data representing each of theagricultural objects may be indexed into a data repository. Further, thedata representing each of the agricultural objects may be received from,or otherwise originate at, a precision agricultural management platform,which may include one or more processors configured to analyze sensordata (e.g., image data) captured from one or more sensors at, forexample, an agricultural treatment delivery system. The sensor data maybe analyzed to validate recently captured sensor data (e.g., for anagricultural object) correlates with at least a subset of indexedagricultural object data (e.g., previously sensed data for a specificagricultural object). Also, the sensor data may be analyzed to determinea stage of growth or any other agriculturally-related condition forwhich a treatment may be applied or delivered. Further, the image datamay be used to form a modified or predicted image of an agriculturalobject at the precision agricultural management platform.

As an agricultural treatment delivery system traverses adjacent toarrangements of agricultural objects (e.g., fruit trees), sensed imagedata from one or more cameras may be compared to data representing apredicted image of the agricultural object. The predicted image may bederived at a precision agricultural management platform to predict achange in an image or physical appearance (or any other characteristic)based on predicted growth of an agricultural object. The predicted imagethen may be used to detect the corresponding agricultural object in ageographic boundary to which a treatment may be applied.

At 306, a mobility platform may be activated to control autonomouslymotion and/or position of an agricultural treatment delivery vehicle. Amobility platform may be configured to implement a map, which mayinclude data configured to position one or more emitters of anagricultural projectile delivery system adjacent to an agriculturalobject within a geographic boundary. Hence, a map may include dataspecifying a location of an indexed agricultural object, and can be usedto navigate a vehicle autonomously to align an emitter with anagricultural object to deliver a treatment.

At 308, an agricultural object may be detected based on or inassociation with one or more sensors (e.g., one or more image capturedevices). Image data of an agricultural object may be generated to forman imaged agricultural object. Then, the imaged agricultural object maybe correlated to data representing an indexed agricultural object in asubset of agricultural objects. A correlation may validate that theimaged agricultural object is a same object as described in dataassociated with the indexed agricultural object. Further, a spatialposition of an imaged agricultural object may be correlated to aposition and/or an orientation of an emitter.

At 310, an emitter from a subset of one or more emitters may be selectedto perform an action. Further, a corresponding action to be performed inassociation with a particular agricultural object may be identified, theagricultural object being an actionable object (e.g., an agriculturalobject for which an action is perform, whether chemical or mechanical,such as robotic pruners or de-weeding devices). In some cases, anoptical sight associated with an emitter may be identified, and acorresponding action may be associated with the optical sight todetermine a point in time to activate emission of an agriculturalprojectile.

At 312, an agricultural treatment may be emitted as a function of apolicy. For example, an emitter may be activated to align an emitter toa spatial position (e.g., at which an agricultural object may bedisposed). Upon alignment, propulsion of an agricultural projectile maybe triggered to intercept an agricultural object.

In an implementation in which a vehicle including an agriculturaltreatment delivery system is controlled manually, logic in associationwith an agricultural treatment delivery system may be configured todetect displacement of the vehicle and compute a spatial position of anemitter. Further, an agricultural treatment delivery system may beconfigured to detect a point or a line (e.g., an optical ray) at which aspatial position of an emitter intersects a path specified by a map. Thepath may be associated with a subset of agricultural objects for whichone or more emitters may be configured to perform a subset of actions.Also, a subset of agricultural objects may be detected in associationwith one or more sensors. A subset of actions may be identified to beperformed in association with a subset of agricultural objects, such asa number of blossoms on one or more trees. One or more emitters may beselected autonomously to perform a subset of actions, whereby one ormore emitters may emit a subset of agricultural projectiles to intercepta subset of agricultural objects. In one instance, at least twodifferent agricultural projectiles may be emitted to perform differentactions.

In a vehicle that includes an agricultural treatment delivery system,and is controlled autonomously, logic in association with anagricultural treatment delivery system may be configured to generatecontrol signals (e.g., at a mobility platform) to drive the vehicleautonomously, compute a spatial position of the vehicle relative to, forexample, an agricultural object, and calculate a vehicular trajectory tointersect a path based on, for example, data representing a map.Further, a spatial position of an emitter may be determined to beadjacent to a path specified by the map, the path also being associatedwith a subset of agricultural objects for which one or more emitters areconfigured to perform a subset of actions. In some examples, a rate ofdisplacement of the vehicle may be adjusted autonomously to, forexample, enhance accuracy, an amount of dosage, or the like. Upon detecta subset of agricultural objects in association with one or moresensors, one or more emitters may be configured to emit a subset ofagricultural projectiles to intercept the subset of agricultural objectsat the rate of displacement.

In at least one implementation, control signals to drive the vehicleautonomously may be supplemented by receiving a first subset of datarepresenting a vehicular trajectory, the data being generating at ateleoperator controller. One or more emitters may emit a subset ofagricultural projectiles responsive to a second subset of dataoriginating at the teleoperator controller.

FIG. 4 is a functional block diagram depicting a system including aprecision agricultural management platform communicatively coupled via acommunication layer to an agricultural treatment delivery vehicle,according to some examples. Diagram 400 depicts a mobility controller447 disposed in an agricultural treatment delivery vehicle 430, which,in turn, may include any number of sensors 470 of any type. One or moresensors 470 may be disposed within, or coupled to, either mobilitycontroller 447 or an agricultural treatment delivery system 420, orboth. Sensors 470 may include one or more Lidar devices 472, one or morecameras 474, one or more radars 476, one or more global positioningsystem (“GPS”) data receiver-sensors, one or more inertial measurementunits (“IMUs”) 475, one or more odometry sensors 477 (e.g., wheelencoder sensors, wheel speed sensors, and the like), and any othersuitable sensors 478, such as infrared cameras or sensors,hyperspectral-capable sensors, ultrasonic sensors (or any other acousticenergy-based sensor), radio frequency-based sensors, etc.

Other sensor(s) 478 may include air flow-related sensors to determinemagnitudes and directions of ambient airflow relative to agriculturaltreatment delivery system 420 and one or more emitters configured toemit an agricultural projectile 412. Air flow-related sensors mayinclude an anemometer to detect a wind speed and a wind vane to detectwind direction. Values of wind speed and direction may be determinedrelative to a direction and velocity of agricultural treatment deliveryvehicle 430, and may further be used to adjust a time at which to emitagricultural projectile 412 and/or modify a trajectory as a function ofwindage (e.g., wind speed and direction). In some cases, wheel anglesensors configured to sense steering angles of wheels may be included asodometry sensors 477 or suitable sensors 478. Sensors 470 may beconfigured to provide sensor data to components of mobility controller447 and/or agricultural treatment delivery vehicle 430, as well as toelements of precision agricultural management platform 401. As shown indiagram 400, mobility controller 447 may include a planner 464, a motioncontroller 462, a motion estimator/localizer 468, a perception engine466, and a local map generator 440. Note that elements depicted indiagram 400 of FIG. 4 may include structures and/or functions assimilarly-named elements described in connection to one or more otherdrawings.

Motion estimator/localizer 468 may be configured to localizeagricultural treatment delivery vehicle 430 (i.e., determine a localpose) relative to reference data, which may include map data, routedata, and the like. Route data may be used to determine path planningover one or more paths (e.g., unstructured paths adjacent to one or moreplants, crops, etc.), whereby route data may include paths, pathintersections, waypoints (e.g., reflective tape or other visual fiducialmarkers associated with a trellis post), and other data. As such, routedata may be formed similar to road network data, such as RNDF-like data,and may be derived and configured to navigate paths in an agriculturalenvironment. In some cases, motion estimator/localizer 468 may beconfigured to identify, for example, a point in space that may representa location of agricultural treatment delivery vehicle 430 relative tofeatures or objects within an environment. Motion estimator/localizer468 may include logic configured to integrate multiple subsets of sensordata (e.g., of different sensor modalities) to reduce uncertaintiesrelated to each individual type of sensor. According to some examples,motion estimator/localizer 468 may be configured to fuse sensor data(e.g., Lidar data, camera data, radar data, etc.) to form integratedsensor data values for determining a local pose. According to someexamples, motion estimator/localizer 468 may retrieve reference dataoriginating from a reference data repository 405, which may include amap data repository 405 a for storing 2D map data, 3D map data, 4D mapdata, and the like. Motion estimator/localizer 468 may be configured toidentify at least a subset of features in the environment to matchagainst map data to identify, or otherwise confirm, a position ofagricultural treatment delivery vehicle 430. According to some examples,motion estimator/localizer 468 may be configured to identify any amountof features in an environment, such that a set of features can one ormore features, or all features. In a specific example, any amount ofLidar data (e.g., most or substantially all Lidar data) may be comparedagainst data representing a map for purposes of localization. In somecases, non-matched objects resulting from a comparison of environmentfeatures and map data may be classify an object as a dynamic object. Adynamic object may include a vehicle, a farm laborer, an animal, such asa rodent, a bird, or livestock, etc., or any other mobile object in anagricultural environment. Note that detection of dynamic objects,including obstacles, such as fallen branches in a path, may be performedwith or without map data. In particular, dynamic or static objects maybe detected and tracked independently of map data (i.e., in the absenceof map data). In some instances, 2D map data and 3D map data may beviewed as “global map data” or map data that has been validated at apoint in time by precision agricultural management platform 401. As mapdata in map data repository 405 a may be updated and/or validatedperiodically, a deviation may exist between the map data and an actualenvironment in which agricultural treatment delivery vehicle 430 ispositioned. Therefore, motion estimator/localizer 468 may retrievelocally-derived map data generated by local map generator 440 to enhancelocalization. For example, locally-derived map data may be retrieved tonavigate around a large puddle of water on a path, the puddle beingomitted from global map data.

Local map generator 440 is configured to generate local map data inreal-time or near real-time. Optionally, local map generator 440 mayreceive static and dynamic object map data to enhance the accuracy oflocally-generated maps by, for example, disregarding dynamic objects inlocalization. According to at least some embodiments, local mapgenerator 440 may be integrated with, or formed as part of, motionestimator/localizer 468. In at least one case, local map generator 440,either individually or in collaboration with motion estimator/localizer468, may be configured to generate map and/or reference data based onsimultaneous localization and mapping (“SLAM”) or the like. Note thatmotion estimator/localizer 468 may implement a “hybrid” approach tousing map data, whereby logic in motion estimator/localizer 468 may beconfigured to select various amounts of map data from either map datarepository 405 a or local map data from local map generator 440,depending on the degrees of reliability of each source of map data.Therefore, motion estimator/localizer 468 may use out-of-date map datain view of locally-generated map data.

In various examples, motion estimator/localizer 468 or any portionthereof may be distributed in or over mobility controller 447 oragricultural treatment delivery system 420 in any combination. In oneexample, motion estimator/localizer 468 may be disposed as motionestimator/localizer 219 a in agricultural treatment delivery system 420.Also, agricultural treatment delivery system 420 may also includesensors 470. Therefore, agricultural treatment delivery system 420 maybe configured to autonomously apply treatments to agricultural objectsindependent of mobility controller 447 (i.e., agricultural treatmentdelivery vehicle 430 may navigate manually). In another example,agricultural treatment delivery vehicle 430 may navigate autonomously.Hence, motion estimator/localizer 468 may be disposed in either mobilitycontroller 447 or agricultural treatment delivery system 420, with itsfunctionalities being shared by mobility controller 447 and agriculturaltreatment delivery system 420. According to some examples, motionestimator/localizer 468 may include NavBox logic 469 configured toprovide functionalities and/or structures as described in U.S.Provisional Patent Application No. 62/860,714 filed on Jun. 12, 2019 andtitled “Method for Factoring Safety Components into a SoftwareArchitecture and Software and Apparatus Utilizing Same.”

Perception engine 466 may be configured to, for example, assist planner464 in planning routes and generating trajectories by identifyingobjects of interest (e.g., agricultural objects) in a surroundingenvironment in which agricultural treatment delivery vehicle 430 istraversing. As shown, perception engine 466 may include an objectdetector 442 a configured to detect and classify an agricultural object,which may be static or dynamic. Examples of classifications with whichto classify an agricultural object includes a class of leaf, a class ofbud (e.g., including leaf buds and fruit buds), a class of blossom, aclass of fruit, a class of pest (e.g., insects, rodents, birds, etc.), aclass of disease (e.g., a fungus) a class of a limb (e.g., including aspur as an object), a class of obstacles (e.g., trellis poles and wires,etc.), and the like. Object detector 442 a may be configured todistinguish objects relative to other features in the environment, andmay be configured to further identify features, characteristics, andattributes of an agricultural object to confirm that the agriculturalobject relates to an indexed agricultural object and/or policy stored inmemory 421. Further, perception engine 466 may be configured to assignan identifier to an agricultural object that specifies whether theobject is (or has the potential to become) an obstacle that may impactpath planning at planner 464. Although not shown in FIG. 4, note thatperception engine 466 may also perform other perception-relatedfunctions, predicting “freespace” (e.g., an amount of unencumbered spaceabout or adjacent an agricultural object) or whether a subset ofagricultural objects (e.g., leaves) may obstruct agricultural projectiletrajectories directed to another subset of agricultural objects (e.g.,blossoms) to calculate alternative actions or agricultural projectiletrajectories. In some examples, object detector 442 a may be disposed inSenseBox logic 442, which may be configured to provide functionalitiesand/or structures as described in U.S. Provisional Patent ApplicationNo. 62/860,714 filed on Jun. 12, 2019 and titled “Method for FactoringSafety Components into a Software Architecture and Software andApparatus Utilizing Same.”

Planner 464 may be configured to generate a number of candidate vehicletrajectories for accomplishing a goal of traversing within a geographicboundary via a number of available paths or routes, and planner 464 mayfurther be configured to evaluate candidate vehicle trajectories toidentify which subsets of candidate vehicle trajectories may beassociated with higher degrees of confidence levels of providingcollision-free paths adjacent one or more plants. As such, planner 464can select an optimal vehicle trajectory based on relevant criteria forcausing commands to generate control signals for vehicle components 450(e.g., actuators or other mechanisms). Note that the relevant criteriamay include any number of factors that define optimal vehicletrajectories, the selection of which need not be limited to reducingcollisions. In some cases, at least a portion of the relevant criteriacan specify which of the other criteria to override or supersede, whilemaintain optimized, collision-free travel. In some examples, planner 464may be include ActionBox logic 465, which may be configured to providefunctionalities and/or structures as described in U.S. ProvisionalPatent Application No. 62/860,714 filed on Jun. 12, 2019 and titled“Method for Factoring Safety Components into a Software Architecture andSoftware and Apparatus Utilizing Same.”

In some examples, motion controller 462 may be configured to generatecontrol signals that are configured to cause propulsion and directionalchanges at the drivetrain and/or wheels of agricultural treatmentdelivery vehicle 430. In this example, motion controller 462 isconfigured to transform commands into control signals (e.g., velocity,wheel angles, etc.) for controlling the mobility of agriculturaltreatment delivery vehicle 430. In the event that planner 464 hasinsufficient information to ensure a confidence level high enough toprovide collision-free, optimized travel, planner 464 can generate arequest to teleoperator controller 404 (e.g., a teleoperator computingdevice), for teleoperator support. In some examples, motion controller462 may be include SafetyBox logic 443, which may be configured toprovide functionalities and/or structures as described in U.S.Provisional Patent Application No. 62/860,714 filed on Jun. 12, 2019 andtitled “Method for Factoring Safety Components into a SoftwareArchitecture and Software and Apparatus Utilizing Same.”

Autonomous vehicle service platform 401 includes reference datarepository 405, a map updater 406, and an object indexer 410, amongother functional and/or structural elements. Note that each element ofautonomous vehicle service platform 401 may be independently located ordistributed and in communication with other elements in autonomousvehicle service platform 401. Further, any component of autonomousvehicle service platform 401 may independently communicate with theagricultural treatment delivery vehicle 430 via the communication layer402. Map updater 406 is configured to receive map data (e.g., from localmap generator 440, sensors 460, or any other component of mobilitycontroller 447), and is further configured to detect deviations, forexample, of map data in map data repository 405 a from alocally-generated map. Map updater 406 may be configured to updatereference data within repository 405 including updates to 2D, 3D, and/or4D map data. Object indexer 410 may be configured to receive data, suchas sensor data, from sensors 470 or any other component of mobilitycontroller 447. According to some embodiments, a classification pipelineof object indexer 410 may be configured to annotate agricultural objects(e.g., manually by a human and/or automatically using an offlinelabeling algorithm), and may further be configured to train a classifier(e.g., on-board agricultural treatment delivery vehicle 430), which canprovide real-time classification of agricultural object types duringautonomous operation. In some examples, object indexer 410 may beconfigured to implement computer vision and machine learning algorithmsto construct and maintain a spatial semantic model (e.g., at resolutionsof sub-centimeter, or less) and/or a time-series model of plantphysiology and state-of-growth. Data representing any of these modelsmay be linked to, or disposed in, data representing indexed agriculturalobject data.

Agricultural treatment delivery system 420 may include hardware orsoftware, or any combination thereof, and may include a memory 421, amotion estimator/localizer 219 a, a target acquisition processor 422, atrajectory processor 424, an emitter propulsion subsystem 426, andcalibration logic 409. Memory 421 may be configured to store policy datato specify an action or treatment for an associated indexed agriculturalobject, and may also store indexed agricultural object data (e.g.,describing a specific agricultural object of interest, includingidentifier data and image data, which may be predicted). Motionestimator/localizer 219 a may be configured to determine a position ofagricultural treatment delivery system 420 or an emitter relative to anagricultural object targeted for treatment. Target acquisition processor422 may be configured to sense or otherwise detect an agriculturalobject, such as a blossom, that may be identified in association withindexed agricultural object data. Hence, target acquisition processor422 may acquire an agricultural object as a target for treatment,whereby an acquired agricultural object may be detected in a subset ofpixels in image data. Trajectory processor 424 may be configured totrack an acquired agricultural object as a subset of pixels in imagedata relative to, for example, an optical sight. In event the trackedsubset of pixels aligns with the optical sight, trajectory processor 424may generate a control signal to initiate delivery of a payload (i.e., atreatment) as agricultural projectile 412. Responsive to receiving acontrol signal, emitter propulsion subsystem 426 may be configured topropel agricultural projectile 412 toward a target. Calibrator 409 mayinclude logic configured to perform calibration of various sensors, suchas image sensors, of the same or different types. In some examples,calibrator 409 may be configured to compute a trajectory direction(e.g., in Cartesian space (x, y, z) and/or orientation of an emitter(e.g., roll, pitch and yaw). As such, a position and orientation of anemitter may be calibrated to intercept a target, such as visual fiducialmarker or a laser light beam on a surface, whereby a pixel associatedwith an optical sight may cause an agricultural projectile 412 to beemitted when a subset of pixels of target in an image aligns with asubset of pixels associate with an optical sight. In this example,alignment of an optical sight to a target may be in line with an opticalray extending through the optical sight.

FIG. 5 is a diagram depicting another example of an agriculturaltreatment delivery system, according some examples. Diagram 500 depictsan agricultural projectile delivery system 581 implemented as anagricultural treatment delivery system, whereby agricultural projectiledelivery system 581 may be configured to detect an agricultural object,identify a course of action (e.g., based on policy data), track an imageof the agricultural object, and emit an agricultural projectile 512 tointercept an agricultural object as a target. Agricultural projectiledelivery system 581 may include one or more image capture devices, suchas a camera 504 and a Lidar 505, the imaged sensor data from each may ormay not be integrated or “fused,” according to various examples. Asshown, one or more image capture devices 504 and 505 may be configuredto capture an image of an agricultural environment 501 in a field ofview of, for example, image capture device 504, the captured image beingreceived into agricultural projectile delivery system 581 via, forexample, sensor data 576, as agricultural environment image 520.

In accordance with some examples, agricultural projectile deliverysystem 581 includes one or more emitters 503 disposed in a field of viewbetween image capture device 504 and objects of interest, such asagricultural objects disposed in agricultural environment 501.Therefore, emitters 503 may be presented as image data 511 inagricultural environment image 520, the image data 511 of emittersthereby occluding images of one or more agricultural objects inagricultural environment 501. In examples in which image data 511obscures or occludes a portion of agricultural environment 501,agricultural projectile delivery system 581 may be configured togenerate optical sights 513 that, at least in some cases, may be coaxialwith an orientation of an aperture of a corresponding emitter. Forexample, an optical sight 513 a may be centered coaxially about a line514 coincident with a trajectory direction of a corresponding aperture.Further, line 514 may be an optical ray extending from at least onepixel in a subset of pixels associated with a center of 513 a (or anyother portion of an optical sight) to a target in agriculturalenvironment 501. In at least one implementation, an emitter may be anozzle and an aperture may refer to a nozzle opening.

Agricultural environment image 520 includes image data representing oneor more agricultural objects, such as objects 522 to 529. Object 522 isa blossom, object 524 is an open cluster, object 525 is a spur, object527 is a leaf or other foliage, and object 529 is a portion of a trunkor stem. Other objects—as agricultural objects—based on agriculturalapplications, associations, and implementations, may be depicted inagricultural environment image 520, such as a post 532, a wire 533, soil534, and a marker 531, among others. Marker 531 may be detected andanalyzed to determine positioning information, to facilitate in-situpositioning or calibration, or to perform any other function.

Note that image frame 509 and image data 511 of emitters 503 may beaffixed to a frame of reference of, for example, an agriculturaltreatment delivery vehicle (not shown) as it travels in direction 543,at least in this example. Therefore, objects within image frame 509including agricultural objects 522 to 529 may traverse agriculturalenvironment image 520 in a direction of image travel 541. Consequently,agricultural objects for which a treatment may be applied may movetoward, for example, an array of optical sights 513 (e.g., to the rightin diagram 500).

Agricultural projectile delivery system 581 may be configured to receivepolicy data 572 to specify an action, a treatment, or the like for anagricultural object, as well as indexed object data 574 to provide data(including imagery data for comparison) that specifies any number ofcharacteristics, attributes, actions, locations, etc., of anagricultural object. Agricultural projectile delivery system 581 mayreceive or derive sensor data 576 (e.g., image data, wind speed data,wind direction data, etc.) as well as position data 578 (e.g., aposition of an agricultural object). Agricultural projectile deliverysystem 581 also may be configured to receive any other types of data.

Agricultural projectile delivery system 581 is shown to include a targetacquisition processor 582, a trajectory processor 583, and an emitterpropulsion subsystem 585. In various examples, target acquisitionprocessor 582 may be able to identify an agricultural object, such asobject 522, that may be correlatable to a subset of indexed agriculturalobject data 574, which may include previously-sensed data and datapredicting an image of the identified agricultural object with apredicted amount of growth. Among other things, a predicted image mayfacilitate image-based identification of a uniquely identifiedagricultural object among many others in geographic location, such as anorchard. Further, target acquisition processor 582 may detect whetherpolicy data 572 specifies whether an action is to be taken. If not, oneor more sensors may monitor and capture data regarding a non-targetedidentified agricultural object. As a non-targeted object, however, itneed not be tracked as a target (e.g., identifying an optical sight maybe omitted as well as a treatment). In some cases, an identifiedagricultural object may be associated with an action, such as object522. Trajectory processor 583 may be configured to select an opticalsight for implementing an action, and may be further configured to trackan identified agricultural object indicated as requiring treatment asits image data traverses in direction 541. Trajectory processor 583 mayalso be configured to predict an emission parameter (e.g., emissiontime) at which an agricultural object aligns with an optical sight. At adetected emission time, trajectory processor 583 may generate a controlsignal to transmit to emitter propulsion subsystem 585, which, in turnmay activate an emitter to propel agricultural projectile 512 tointercept object 522 at a calculated time.

FIG. 6 is an example of a flow diagram to align an emitter to a targetautonomously, according to some embodiments. Flow 600 begins at 602, atwhich sensor data representing presence of agricultural objects disposedin an agricultural environment may be received. In some examples, animage capture device, such as a camera, may capture an image of one ormore agricultural objects in a subset of agricultural objects. Also,image data representing a number of agricultural objects in a field ofview of an image capture device may be received at 602. Consider thatthe one or more agricultural objects are blossoms. The image capturedevice may receive light (e.g., reflective sunlight) from anagricultural object in a field of view of image capture device. Imagedata representing the agricultural object may be captured at any rate(e.g., 30 frames a minute, or fewer or more). In one example, reflectivelight may be received from an agricultural object in one or more timeintervals during which reflective light is visible (e.g., within avisible light spectrum, such as when sunlight is available). In otherexamples, the reflected light received into an image capture device maybe infrared light or any other spectrum of light. As such, anagricultural treatment delivery system may operate in the absence ofsunlight. In at least one embodiment, one or more emitters may bedisposed in between an image capture device and an agricultural object.For example, one or more emitters may be disposed or positioned in afield of view of a camera, whereby an aperture of an emitter (e.g.,aperture of a nozzle) may be aligned coaxially with an optical raycorresponding to a pixel at the center of aperture of an emitter in acaptured image. In other examples, an aperture of an emitter need not bealigned coaxially with an optical ray.

At 604, an agricultural object may be identified as, for example, abloom that is associated with indexed agricultural object data, whichmay include previously captured image data and an identifier thatuniquely distinguishes the identified agricultural object from otheragricultural objects throughout, for example, an orchard. A subset ofagricultural objects may also be captured as image data in a field ofview.

At 606, a determination is made as to whether an identified agriculturalobject is correlatable to indexed data (e.g., previously sensed dataregarding the agricultural object that may be processed and indexed intoa data arrangement stored in a data repository). In no, flow 600 movesto 612. If yes, flow 600 may move to 608 to determine, optionally, aspatial location of an identified agricultural object, as a function ofa position of an agricultural treatment delivery vehicle or an emitter.At 610, a spatial location of the identified agricultural object may becompared to location data in indexed agricultural object data to analyzewhether the identified agricultural object is correlated to indexed data(i.e., the identified agricultural object and indexed agriculturalobject data relate to the same object).

At 612, an action may be associated to data representing the identifiedagricultural object. For example, policy data may be linked to indexedagricultural object data, which may specify a first policy to germinateking blossoms and a second policy to terminate lateral blossoms, wherebythese two policies may be implemented individually or in combination(simultaneously or nearly simultaneously). For example, consider that anidentified agricultural object is identified using indexed data or otherimage processing that predicts a classification for the identifiedagricultural object, whereby the identified agricultural object ispredicted to be a “king blossom.” Therefore, an action relating to thefirst policy (e.g., germination) may be linked to the identifiedagricultural object to perform that action. Note that a subset ofagricultural objects of the same or different classifications (or types)may be detected in a field of view and correlated to one or morecorresponding actions to be performed in association with one or moreemitters.

At 614, an identified agricultural object may be locked onto and trackedas a target for applying a treatment. In some cases, one or more opticalsights may configured to detect alignment with one or more identifiedagricultural objects.

At 616, each optical sight may be predicted to align with an associatedagricultural object at 616, the optical sight being associated with anemitter. In particular, an optical sight may be selected to align with atarget relative to other optical sights, the optical sight beingassociated with an emitter for applying a treatment to a correspondingidentified agricultural object. In some cases, an emitter is oriented toemit an emission parallel (e.g., coaxially) with an optical rayextending from an optical sight to a target, the optical sight beingassociated with one or more pixels of an image capture device. Further,one or more agricultural objects may be tracked relative to one or moreoptical sights. For example, reflective light from one or more of theagricultural objects may be tracked in a field of view of an imagecaptured by a camera. A field of view of an image capture device may bea parameter (e.g., an angle) through which observable light orelectromagnetic radiation may be captured in an image, according to someexamples. Also, the reflective light from an agricultural object can becaptured in an image and tracked in association with a visible imageportion (e.g., a non-occluded image portion).

At 618, a trajectory of an agricultural projectile may be computed(e.g., relative to an emission parameter). In other examples, atrajectory of an agricultural projectile may be computed to adjust anorientation of an emitter, at least in one instance.

At 620, a value of an elapsed time to alignment of an optical sight toan agricultural object may be calculated and tracked. Based on avelocity of an agricultural treatment delivery vehicle, a time to emitan agricultural projectile may be computed and tracked. Hence, trackingan optical sight relative to an agricultural object may be a function ofa rate of displacement of one or more emitters or a vehicle (e.g.,relative to the soil or the agricultural environment). Further, aportion of the value of the elapsed time may be calculated. The portionof the elapsed time value may describe an amount of time during whichthe agricultural object is associated with an occluded image portion.

At 622, a determination is made as to whether any of sensor data detectsa variance, such as a change in emitter altitude (e.g., a bump or raisedelevation, or dip or depression) or any other change in sensor data,such as a variation in vehicle speed. If there is a variance, atrajectory may be recomputed at 624 (e.g., recomputing an emissionparameter associated with the trajectory). For example, if a change inemitter altitude changes relative to the ground, an initial opticalsight may be misaligned. Thus, another optical sight may be selected at626. But if there is no variance, flow 600 moves from 622 to 628.

At 628, an agricultural object can be predicted to align with an opticalsight to form a predicted emission parameter, which may be monitored todetect alignment of an optical sight and a target. The predictedemission parameter may be tracked in association with agriculturalobject. For example, a predicted emission parameter may be a predictedemission time, either a duration or elapsed amount of time, or a pointin time at which alignment occurs, thereby providing a trajectory via,for example, an optical ray. Further, alignment of an agriculturalobject with an optical sight may be detected at the predicted emissionparameter.

At 630, an emitter is activated to apply an action based on a predictedemission parameter. Thus, emission of an agricultural projectile may betriggered at a predicted emission time. In one example, an emission timemay specify a time at which a pixel associated with an optical sight isaligned with an optical ray that extends from the pixel to at least aportion of a targeted agricultural object.

FIGS. 7A and 7B depict examples of data generated to identify, track,and perform an action for one or more agricultural objects in anagricultural environment, according to some examples. FIG. 7A is adiagram depicting an image frame 700 in which an agriculturalenvironmental image 720 a includes agricultural objects identified astargets 722 a, 722 b, 722 c, 722 d, 722 e, 722 f, 7ddg, 722 h, 722 j,724 a, and 724 b. In various examples, agricultural environmental image720 a may be presented to a user in a graphical user interface (notshown), or may represent data calculations, derivations, functions, andthe like based on image data and other data. Agricultural environmentalimage 720 a also includes image data 711 a representing emitters andcorresponding optical sights, such as optical sights 726 a, 726 b, 726c, 726 d, 726 e, 726 f, and 726 g.

An agricultural projectile delivery system (not shown) may be configuredto identify and select optical sight 726 a (and corresponding emitter)to apply a treatment to target 722 a. Further, agricultural projectiledelivery system may be configured to identify and select optical sights726 b, 726 c, 726 d, 726 e, 726 f, 726 g, and 726 g to emit agriculturalprojectiles to targets 722 e, 722 f, 722 b, 722 g, 722 c, 722 h, and 722d, respectively. Note that optical sight 726 g may be configured topropel an agricultural projectile to both target 722 h and target 722 dat, for example, different alignments. Note that dotted lines 723 mayrepresent data configured to specify a distance 727 (e.g., a number ofpixels) or a time until a target aligns with an optical sight. Solidlines 725 represent data configured to specify a distance or timesubsequent to a treatment, as applied to targets 724 a and 724 b. Bothtargets 724 a and 724 b are depicted with crosshatch to signify that oneor more treatments have been performed. Any of the above-describedactions may be performed by hardware and/or software that providefunctionality to an agricultural projectile delivery system. FIG. 7Adepicts targets 722 g, 724 a, and 724 b being occluded by image data 711a of emitters at a first point in time, t1.

FIG. 7B is a diagram depicting an image frame 750 depicting an imageframe 750 in which an agricultural environmental image 720 b includesagricultural objects identified as targets 722 a, 722 b, 722 c, 722 d,722 e, 722 f, 7ddg, 722 h, 722 j, 724 a, and 724 b, as well as targets772 x, 772 y, and 772 z, whereby targets 772 e, 772 b, 772 g, and 772 jare occluded or partially occluded by image data 711 b of an array ofemitters. Agricultural environmental image 720 b depicts a state inwhich targets 724 a, 724 b, 772 f, 772 e, 772 g, 772 h, and 772 j havereceived treatment by at least at time, t2. These treated targets aredepicted in crosshatch. Targets identified at time, t2, includingtargets 772 x, 772 y, and 772 z, may be calculated to receive treatmentat or within time, t3. As such, targets 772 x, 772 y, and 772 z havebeen associated with optical sights, such as 776 z, to detect alignmentand trigger propulsion of agricultural projectiles to apply varioustreatments.

FIG. 7C is a diagram depicting parameters with which to determineactivation of an emitter to apply a treatment, according to someexamples. FIG. 7C depicts an image capture device 774 capturing imagedata representing an agricultural environment 770, which includes atarget 777 z, and image data representing an array of emitters 711 cdisposed in a field of view of image capture device 774. Hence, imagecapture device 774 may be configured to generate an agriculturalenvironment image 720 a within an image frame 750 a. Logic of anagricultural projectile delivery system may be configured to identifyvisible image fields 785 a and 785 b in which one or more agriculturalobjects, such as target 777 za, are visible (i.e., not occluded).Therefore, digitized or pixelated image data associated with targets,such as target 777 za, may be observed, identified, and tracked, amongother things. Logic of an agricultural projectile delivery system alsomay be configured to identify occluded image field 787 a associated withimage data 711 bb of emitter 711 c. While pixelated data associated withtarget 777 za may be tracked in visible image field 785 a, it may becomeoccluded as motion moves the image of target 777 za to an optical sight776 za.

In at least one example, an agricultural projectile delivery system maybe configured to identify target 777 za and one or more pixelsassociation therewith (e.g., as a pixelated target 777 zb). Theagricultural projectile delivery system may also be configured to derivea predicted emission parameter 790 (e.g., a predicted time) that may beused determine a point in time to activate an emitter to propel aprojectile to a target. Further, an agricultural projectile deliverysystem may also be configured to determine a visible parameter 791 aduring which visible target pixels 780 a may be analyzed to track,evaluate, and modify predicted emission parameter 790 (e.g., changes invehicle speed, a gust of wind, or the like). The agricultural projectiledelivery system may computationally predict an occluded parameter 791 bduring which occluded target pixels 780 b may not be visible due tooccluded image field 787 a associated with image data 711 b of theemitters. As pixels of target 777 za travel to optical sight 776 za inan occluded image field 787, a rate at which a pixel of a target 777 zamay align with optical sight 776 za may be modified based on sensor data(e.g., vehicle speed), which, in turn, may modify data valuesrepresenting occluded parameter 791 b, thereby modifying an emissiontime.

FIG. 8 is a diagram depicting a perspective view of an agriculturalprojectile delivery vehicle configured to propel agriculturalprojectiles, according to some examples. Diagram 800 depicts anagricultural projectile delivery vehicle 810 traveling in a direction ofmotion 813 at a distance 815. Further, diagram 800 depicts anagricultural projectile delivery system 811 detecting blossoms astargets 722 f, 724 b, and 724 a of FIG. 7B and propels agriculturalprojectiles 812, 814, and 813 to intercept respective targets. In someexamples, each of agricultural projectiles 812, 814, and 813 each may beemitted at any angle along a trajectory that lies in a plane thatinclude an optical ray, such as optical ray 877.

FIG. 9 is a diagram depicting an example of trajectory configurations tointercept targets autonomously using an agricultural projectile deliveryvehicle, according to some examples. Diagram 900 depicts an agriculturalprojectile delivery vehicle 910 including an agricultural projectiledelivery system 952 a configured to propel agricultural projectiles,such as agricultural projectile 912, at any angle 909 relative to plane911. One or more emitters of agricultural projectile delivery system 952a may be configured to propel agricultural projectiles via one or moretrajectories 999 to intercept any target 722 f relative to any heightabove ground. As shown, agricultural projectile delivery system 952 amay be configured to propel agricultural projectile 912 with a forcehaving a vertical component (“Fvc”) and a horizontal component (“Fhc”).As shown, the vertical component of the propulsion force may be in adirection opposite than the force of gravity (“Fg”). Note thathorizontal component (“Fhc”) may have a magnitude sufficient to propelagricultural projectile 912 over a horizontal distance to target 722 f.According to some examples, agricultural projectile delivery vehicle 910may include an agricultural projectile delivery system 952 b configuredto apply treatments via one or more trajectories 954 within a space 950.Therefore, agricultural projectile delivery vehicle 910 may beconfigured to identify agricultural objects along both sides ofagricultural projectile delivery vehicle 910. For example, agriculturalprojectile delivery vehicle 910 may be configured to identify groups 990and 991 of agricultural objects (e.g., fruit trees) and maysimultaneously apply a treatment or different treatments to either sideas agricultural projectile delivery vehicle 910 traverses a path (in theX-direction) between groups 990 and 991 of agricultural objects.

FIG. 10 is a diagram depicting examples of different emitterconfigurations of agricultural projectile delivery systems, according tosome examples. Diagram 1000 depicts an agricultural projectile deliveryvehicle 1010 having at least two exemplary configurations, each of whichmay be implemented separately (e.g., at different times). Configuration1001 includes an agricultural projectile delivery system 1052 a havingany number of emitters configured to emit agricultural projectilessubstantially horizontally (e.g., orthogonal or substantially orthogonalto a direction of gravitational force) to target agricultural objects722 f Configuration 1002 includes a boom 1060 configured to support anagricultural projectile delivery system 1012 configured to identify,monitor, track, and apply a treatment via an agricultural projectile toone or more agricultural objects constituting row crops, such as soybeanplant 1061 a and soybean plant 1061 b, or portions thereof.

FIG. 11 is a diagram depicting yet another example of an emitterconfiguration of an agricultural projectile delivery system, accordingto some examples. Diagram 1100 depicts an agricultural projectiledelivery vehicle 1110 having an exemplary configuration in whichemitters may be configured to propel an agricultural projectile via anytrajectory 1112 from an encompassing structure 1125, which may beconfigured to apply treatments to any nut or fruit tree having threedimensions of growth. As shown, encompassing structure 1125 may havearticulating members that can be positioned in either arrangement 1160 aor 1160 b. The articulating members may include emitters to apply one ormore treatments to one or more agricultural objects associated with athree dimensional vegetative structure, such as an orange tree or walnuttree. The configuration shown in diagram 1100 is not limiting and anyconfiguration of agricultural projectile delivery system may be used toapply treatments to tree 1190.

FIGS. 12 and 13 are diagrams depicting examples of a trajectoryprocessor configured to activate emitters, according to some examples.Diagram 1200 of FIG. 12 includes a rear view of an array of emitters1211 and a side view of an agricultural projectile delivery system 1230.As shown in the rear view, array of emitters 1211 is disposed in a fieldof view of an image capture device 1204. In particular, array ofemitters 1211 may be interposed between a scene being imaged (e.g.,agricultural environment 1210, which includes targets 1222 a) and imagecapture device 1204. In some examples, image capture device 1204 may beconfigured to be “in-line” with optical sights 1214 to determinealignment of an optical sight with a target, such as target 1222 a. Indiagram 1200, an array of emitters 1211 include groups 1219 of emittersthat are each positioned offset in an X-direction and a Y-direction.Note, however, arrangements of emitters into groups 1219 of emitters isa non-limiting example as array of emitters 1211 may each be arranged inany position and in any orientation. Also shown in the rear view, arrayof emitters 1211 is opaque (e.g., depicted as a shaded region) andoccludes images in agricultural environment 1210.

Diagram 1200 also depicts an agricultural environment image 1220, whichmay be generated by image capture device 1204 and disposed within imageframe 1250. Agricultural environment image 1220 includes image data 1279representing emitters and corresponding optical sights, such as anoptical sights 1226 a. As array of emitters 1211 traverses inagricultural environment 1210, images of target 1222 a, such as targetimage 1222 b in a first position may travel to a second position astarget image 1222 c (e.g., a position at which target 1222 a inagricultural environment 1210 may be occluded).

Diagram 1200 also includes a trajectory processor 1283, which may beconfigured to track positions of target image 1222 b and to determine adistance 1227 (or any other parameter, including time) at which an imageof the target (i.e., target image 1222 c) aligns with optical sight 1226a. Target processor 1283 may also be configured to calculate and monitordeviations of predicted distance (“D”) 1203 during which target 1222 maybe occluded by array of emitters 1211. Predicted distance 1203 maycorrelate to a time from which target 1222 a becomes occluded untilalignment with an optical sight 1226 a. Trajectory processor 1283 maydetect a point in time at which target image 1222 c aligns (or ispredicted to align) with optical sight 1226 a, and in response,trajectory processor may generate control data 1229. Control data maytransmitted to an emission propulsion system (not shown) in emitter1230. In addition, control data 1229 may include executable instructionsor any data configured to activate emitter 1213 b to propel agriculturalproject 1212 to intercept 1222 d.

FIG. 13 depicts a trajectory processor 1383 configured to operatesimilarly or equivalently as trajectory processor 1283 of FIG. 12.Diagram 1300 of FIG. 13 includes a rear view of an array of emitters1311 and a side view of an agricultural projectile delivery system 1330.As shown in the rear view, array of emitters 1311 may be disposed in afield of view of an image capture device 1304. Therefore, array ofemitters 1311 may be positioned between an agricultural environment1310, which includes targets 1322 a, and image capture device 1304. Indiagram 1300, an array of emitters 1311 are arranged in a line (orsubstantially in a line) in a Y-direction. Note that in some cases,array of emitters 1311 may be arranged in an X-direction. In thisexample, a predicted distance (“D”) 1303 during which a target 1322 amay be occluded may be less than, for example, predicted distance 1203of FIG. 12, thereby enhancing or prolonging visibility of target 1322 aas it traverses within an image. According to other examples, eachemitter may be arranged in any position and in any orientation. Alsoshown in the rear view, array of emitters 1311 is depicted with shadingto represent that is may be opaque, and may occlude images inagricultural environment 1310.

Diagram 1300 also depicts an agricultural environment image 1320,generated by image capture device 1304 and disposed within image frame1350. Agricultural environment image 1320 includes image data 1379representing emitters and corresponding optical sights, such as anoptical sight 1326 a. As array of emitters 1311 traverses in anagricultural environment 1310, images of target 1322 a, such as targetimage 1322 b in a first position may travel to a second position astarget image 1322 c (e.g., a position at which target 1322 a inagricultural environment 1310 may be occluded).

Diagram 1300 also includes a trajectory processor 1383, which may beconfigured to track positions of target image 1322 b and to determine adistance 1327 (or any other parameter, including time) at which an imageof the target (i.e., target image 1322 c) aligns with optical sight 1326a. Target processor 1383 may also be configured to calculate and monitordeviations of predicted distance (“D”) 1303 during which target 1322 maybe occluded by array of emitters 1311. Predicted distance 1303 maycorrelate to a time from which target 1322 a becomes occluded untilalignment with an optical sight 1326 a. Trajectory processor 1383 maydetect a point in time at which target image 1322 c aligns (or ispredicted to align) with optical sight 1326 a, and in response,trajectory processor 1383 may generate control data 1329. Control datamay be transmitted to an emission propulsion system (not shown) inemitter 1330. In addition, control data 1329 may include executableinstructions or any data configured to activate emitter 1313 b to propelagricultural project 1312 to intercept 1322 d.

FIG. 14 is a diagram depicting an example of components of anagricultural projectile delivery system that may constitute a portion ofan emitter propulsion subsystem, according to some examples. Diagram1400 includes an agricultural projectile delivery system 1430 thatincludes a number of emitters 1437 (or portions thereof), as well as atleast on in-line camera 1401, according to some implementations.

In one example, agricultural projectile delivery system 1430 may includea storage for compressed gas (“compressed gas store”) 1431, which maystore any type of gas (e.g., air), a gas compressor 1432 to generate oneor more propulsion levels (e.g., variable levels of pressure), and apayload source 1433, which may store any treatment or payload (e.g., aliquid-based payload), such as fertilizer, herbicide, insecticide, etc.In another example, agricultural projectile delivery system 1430 mayomit compressed gas store 1431 and gas compressor 1432, and may includea pump 1434 to generate one or more propulsion levels with which topropel a unit of payload source 1433. In various implementations, one ormore of the components shown in agricultural projectile delivery system1430 may be included or may be omitted.

Agricultural projectile delivery system 1430 may also include any numberof conduits 1435 (e.g., hoses) to couple payload source 1433 to a numberof activators 1436, each of which is configured to activate to deliver aunit of payload as, for example, an agricultural projectile, to anidentified target. To illustrate operation, consider that control data1470 is received into agricultural projectile delivery system 1430 tolaunch one or more units of treatment or payload. Logic in agriculturalprojectile delivery system 1430 may be configured to analyze controldata 1470 to that identify activator 1441 is to be triggered at a pointin time, or at a position that aligns a corresponding emitter 1442 totarget 1460. When activated, activator 1441 may release an amount ofpayload (e.g., a programmable amount) with an amount of propulsion(e.g., a programmable amount), thereby causing emitter 1442 to emit aprojectile 1412. According to some examples, agricultural projectiledelivery system 1430 may be adapted for non-agricultural uses, and maybe used to deliver any type of projectile, including units of solids orgases, for any suitable application.

FIG. 15 is a diagram depicting an example of an arrangement of emittersoriented in one or more directions in space, according to some examples.Diagram 1500 includes an arrangement of emitters 1537, one or more ofwhich may be oriented at an 1538 relative to, for example, the ground.Alternatively, one or more subsets of emitters 1537 may be oriented inany angle in the Y-Z plane, any angle in the X-Z plane, or at any angleor vector in an X-Y-Z three-dimensional space. In some examples, one ormore optical arrays aligned with emitters 1537 may intersect at one ormore locations in space, at which an image capture device may bedisposed.

FIG. 16 is a diagram depicting an example of another arrangement ofemitters configured to be oriented in one or more directions in space,according to some examples. Diagram 1600 includes an arrangement ofemitters 1637, whereby one or more emitters may be configurable toadjust one or more orientations to implement agricultural projectiletrajectories in any direction. In this example, a subset of emitters1637 is depicted to include emitters 1639 a, 1639 b, 1639 c, and 1639 dbeing oriented to, for example, select a trajectory that may optimallydeliver a treatment to a target. In some implementations, orientationsof each of emitters 1639 a, 1639 b, 1639 c, and 1639 d may be configuredto deliver at least one agricultural projectile 1612 in the presence ofobstructive objects 1640, such as a cluster of blossoms growing over andin front of (e.g., in between) a target agricultural object 1699. Asshown, obstructive objects 1640 obstruct trajectories 1690 associatedwith emitters 1639 a, 1639 b, and 1639 c. Thus, an orientation and/or aposition of emitter 1639 d facilitates implementing an unobstructedtrajectory over which to propel agricultural object 1612 to intercepttarget objects 1699.

In some examples, emitters 1639 a, 1639 b, 1639 c, and 1639 d may eachbe associated with a camera, such as one of cameras 1641 a, 1641 b, 1641c, and 1641 d. Cameras 1641 a, 1641 b, 1641 c, and 1641 d may beimplemented to detect alignment (e.g., unobstructed alignment) with atarget. Note that while diagram 1600 depicts cameras 1641 a, 1641 b,1641 c, and 1641 d adjacent to corresponding emitters, any of cameras1641 a, 1641 b, 1641 c, and 1641 d may be implemented as “in-line”cameras in which an emitter is disposed in a field of view.

According to various examples, emitters 1639 a, 1639 b, 1639 c, and 1639d may have configurable orientations that may be fixed duringapplication of treatments. In other examples, one or more of emitters1639 a, 1639 b, 1639 c, and 1639 d may have programmable or modifiableorientations or trajectories. As shown, an alignment device 1638 mayinclude logic and one or more motors to orient an emitter to align atrajectory in any direction in three-dimensional space. As such,alignment device 1638 may be configured to modify orientations ofemitters in-situ (e.g., during application of treatments).

FIG. 17 is a diagram depicting one or more examples of calibrating oneor more emitters of an agricultural projectile delivery system,according to some examples. Diagram 1700 includes an in-line camera 1701and an agricultural projectile delivery system 1730 including any numberof emitters, such as emitter 1713, disposed in the field of view ofin-line camera 1701. Diagram 1700 also includes a target 1760 disposedon surface 1703 and calibration logic 1740, which may include hardwareand/or software to facilitate calibration of a trajectory of emitter1713 to guide an emitted agricultural projectile 1712 via a calibratedtrajectory to intercept target 1760. In calibration mode, emitter 1713may be identified or selected for calibration. In some examples, anagricultural projectile trajectory associated with emitter 1713, such asuncalibrated trajectory 1719, may be adjusted to align, for example,coaxially with an optical ray 1717. In at least one alternative example,a timing of activation (e.g., a trigger or activation event at a pointin time or within a time interval) may be calibrated to causeagricultural projectile 1712 to optimally intercept target 1760 within arange of accuracy and precision. In other examples, any otheroperational characteristic of either emitter 1713 or agriculturalprojectile delivery system 1730 may be calibrated, including, but notlimited to, pressure, time-of-flight, rates of dispersal, windage (e.g.,to compensate for airflow, whether vehicle-based or wind), etc.

Diagram 1700 also depicts an in-line targeting image 1720 generated byin-line camera 1701. As a number of emitters are disposed in the fieldof view of in-line camera 1701, a portion of optical ray 1717 may be anoccluded portion 1717 a. In-line targeting image 1720, which is a subsetof image data, includes image data representing an emitter array 1730 athat may occlude visibility to target 1760. Also included is image datarepresenting an optical sight image 1713 b. Calibration logic 1740 maybe configured to access image data to calculate adjustment parameters.In some examples, calibration logic 1740 may be configured to compute analignment (or associated calibration parameters) of one or more pixelsassociated with optical sight image 1713 b to target 1760, and throughone or more points in space associated with an aperture of emitter 1712.Hence, each of optical sight image 1713 b, emitter 1713, and target 1760may be calibrated to lie (or substantially lie) on an optical ray 1717,thereby forming a calibrated trajectory. In some examples, any emittermay be calibrated to coaxially align with any optical ray that extendsfrom any optical sight to a corresponding target. As such, one or moreemitters may be calibrated within a two dimensional plane that mayinclude optical rays extending from optical sight images (and pixelsthereof) at different angles.

In a first calibration implementation, calibration logic 1740 may beconfigured to calculate or predict a projectile impact site 1762 atsurface 1703 that may be relative to a reference of alignment. In atleast some examples, a focused light source may be implemented toprovide a reference alignment mark. In one implementation, a focusedlight source may project coherent light, such as generated by a laser1715 (e.g., a laser pointer or other generator of a beam of laserlight), as a reference mark onto surface 1703. To calibrate emitter1713, a laser 1715 may be affixed in relation to uncalibrated trajectory1719 of emitter 1713 so that emitted laser light terminates or impingeson surface 1703 (i.e., forms a reference mark) that coincides with aprojectile impact site 1762 if projectile 1712 was propelled to impactsurface 1703. Hence, a point on surface 1703 at which coherent lightimpinges may be aligned with projectile impact site 1762. In thisconfiguration, a direction of emitted laser light and a direction ofemitter 1713 may be varied in synchronicity to adjust a predicted impactsite 1762 (i.e., reflected laser light) to coincide with target 1760,which may be aligned with optical array.

In some examples, calibration logic 1740 may be configured to accessin-line targeting image data 1720, or any other image data, to receiveimage data depicting reflected laser light emanating from predictedprojectile impact site 1762. Calibration logic 1740 may be configured tocalculate one or more calibration parameters to align predictedprojectile impact site 1762 with optical ray 1717. For example,calibration logic 1740 may calculate calibration parameters that includean elevation angle and/or an elevation distance 1761 (e.g., in a Y-Zplane) as well as an azimuthal angle and/or an azimuthal distance 1763(e.g., in an X-Z plane). In at least one implementation, a direction ofemission of emitter 1713 may be adjusted to align reflected laser lightwith optical ray 1717 by, for example, adjusting direction of anaperture of a nozzle. Therefore, predicted impact site 1762 may beadjusted by an elevation angle and an azimuthal angle to coincide withtarget 1760. Note that adjusting projectile impact site image 1762 b maycause it to become occluded in image 1720 as it is aligned with targetimage 1760 b.

In at least one case, to confirm calibration, a confirmatoryagricultural projectile 1712 may be propelled to confirm sufficientcalibration upon intercepting target 1760. Calibration logic 1740 may beconfigured to detect impact of confirmatory agricultural projectile 1712at target 1760, and if adjustment may be available, then calibrationlogic 1740 may further compute calibration parameters. Target 1760 maybe implemented at a horizontal distance from emitter 1713, thehorizontal distance being perpendicular or substantially perpendicularto a direction of gravity.

In a second calibration implementation, a visual fiducial marker (notshown) may be attached to a back of each emitter 1713, and an alignmentarm (not shown) may be coupled to each emitter such that an alignmentarm may be configured to rotate a nozzle. The alignment arm may bemanually or autonomously rotated to cause visual fiducial marker tobecome visible an image. When visible, calibration logic 1740 may deememitter 1713 (e.g., a nozzle) aligned with optical ray 1717. Thisimplementation enables servoing to effectuate calibration using image1720, with optional use of target 1760.

In yet another calibration implementation, one or more cameras, such asAR camera 1703, may be implemented with in-line camera 1701 to calibratean emitter trajectory, whereby AR camera and in-line camera 1701 maycapture imagery in synchronicity. In this example, AR camera 1703 may beconfigured to facilitate imagery with augmented reality (“AR”). Hence,AR camera 1703 may be configured to generate a virtual target image 1762a for target 1760 in calibration target image 1722. As shown,calibration target image 1722 includes a virtual target image 1762 athat may include one or more image pixels 1770 that coincide withoptical sight 1713 b. As shown, virtual target image 1762 a is notoccluded by an array of emitters. Therefore, projectile impact siteimage 1760 a, which may be identified by reflective laser light, mayfacilitate adjustment to align with virtual target image 1762 a. Whenaligned, optical sight 1713 b, aperture direction of emitter 1713, andtarget 1760 may be aligned with optical ray 1717. In thisimplementation, calibration target image 1722 omits occluded imageryassociated with image 1720.

FIG. 18 is a diagram depicting another one or more examples ofcalibrating one or more emitters of an agricultural projectile deliverysystem, according to some examples. Diagram 1800 includes an in-linecamera 1801 and an agricultural projectile delivery system 1830including any number of emitters, such as emitter 1813, disposed in thefield of view of in-line camera 1801. Diagram 1800 also includes one ormore light sources 1862 disposed on surface 1803, such as light sources1862. In some examples, light sources 1862 may be reflective light(e.g., reflective laser light) originated at points 1863 a and 1863 b(lasers not shown). Diagram 1800 includes calibration logic 1840 thatmay include hardware and/or software configured to facilitatecalibration of a trajectory 1815 of emitter 1813 to guide an emittedagricultural projectile via a calibrated trajectory to intercept atarget (not shown). In calibration mode, emitter 1813 may be identifiedor selected for calibration. In some examples, an agriculturalprojectile trajectory 1815 associated with emitter 1813 may be adjustedto align, for example, coaxially with an optical ray 1817.

In this example, emitter 1813 may be coupled (e.g., rigidly) to one ormore boresights 1814. As shown, boresight 1814 a and boresight 1814 bare affixed at a distance 1811 to emitter 1813, and each boresightincludes an interior space through which light may pass as a boresightis aligned with a source of light (or beam of light). In some examples,each interior space of boresight 1814 a and boresight 1814 b may beoriented coaxially with a line in three-dimensional space at any angle,regardless whether boresight 1814 a and boresight 1814 b are similarlyor differently oriented. In this configuration, boresight 1814 a andboresight 1814 b are oriented such that when corresponding sources oflight passes through each, emitter 1813 is deemed aligned with opticalray 1817. For example, if beams of light 1818 a and 1819 b, originatingat respective sources of light 1862, are detected to pass throughboresight 1814 a and boresight 1814 b, respectively, a trajectory foremitter 1813 is aligned with optical ray 1817. Note that distance 1811may be sufficient to enable beams of light 1818 a and 1819 b to passthrough boresight 1814 a and boresight 1814 b, respectively, and bedetectable as aligned beam images 1818 b and 1819 b, respectively, inin-line targeting image 1820.

Diagram 1800 also depicts an in-line targeting image 1820 generated byin-line camera 1801. As a number of emitters are disposed in the fieldof view of in-line camera 1801, a portion of optical ray 1817 may be anoccluded portion. In-line targeting image 1820, which is a subset ofimage data, includes image data representing an emitter array 1830 athat may occlude visibility to a target. Also included is image datarepresenting an optical sight image 1813 b. Calibration logic 1840 maybe configured to access image data, such as aligned beam images 1818 band 1819 b, to calculate adjustment parameters to align boresight 1814 aand boresight 1814 b to beams of light 1818 a and 1819 b, therebycausing alignment of emitter 1813 coaxially to optical ray 1817.Calibration logic 1840 may further be configured to detect aligned beamimages 1818 b and 1819 b during calibration to indicate projectiletrajectory 1815 is aligned.

FIG. 19 is an example of a flow diagram to calibrate one or moreemitters, according to some embodiments. Flow 1900 begins at 1902. At1902, a calibration mode is entered to calibrate one or more emittersduring which a trajectory of an emitter (e.g., a nozzle) may be adjustedto intercept a target, such as an agricultural object. In calibrationmode, hardware and/or software may be configured to implementcalibration logic to facilitate calibration. In calibration mode, anemitter of an agricultural projectile delivery system may be identifiedor otherwise selected for calibration. For example, an emitter may beadjusted to calibrate a trajectory of an agricultural projectile tointercept a target. Hence, an uncalibrated trajectory may be adjusted toalign, for example, coaxially with an optical ray, at least in someexamples.

At 1904, a determination is made as to whether multiple cameras may beused during calibration. For example, at least one additional camera maybe used to generate augmented reality-based imagery. If no, flow 1900continues to 1906, at which focused light sources may be implemented tocalibrate alignment. Examples of focused light sources include coherentlight sources (e.g., laser light sources), or any other type of lightsource. At 1908, a determination is made as to whether one or moreboresights may be implemented. If not, flow 1900 continues to 1910, atwhich a laser beam may be aligned with an emitter aperture (e.g.,trajectory) direction to align to a reference mark (e.g., laser light)that may be coincident to a predicted projectile impact site (e.g., viathe trajectory). A determination is made at 1912 as to whether areference laser light coincides with a target, which may be aligned withan optical ray. If there is not a deviation, then an emitter trajectorymay be deemed calibrated. But if there is a deviation, flow 1900continues to 1914 at which one or more calibration parameters may bedetermined (e.g., elevation-related parameters, azimuthal-relatedparameters, and the like). At 1916, emitter (e.g., nozzle) may beadjusted relative to a number of elevation degrees or azimuthal degrees,and flow 1900 continues to determine if another calibration adjustmentresults in calibration.

Referring back to 1908, if a determination indicates a boresight isimplemented, flow 1900 continues to 1930. At 1930, one or moreboresights may be implemented with an emitter. In some cases, one ormore boresights may be oriented with one or more lines, and may berigidly affixed to an emitter. In other cases, one or more boresightsneed not be rigidly affixed and may be adjustably moveable relative toan emitter. At 1932, one or more light sources may be identified foralignment, the light being reflective light from one or more lasers. At1934, an emitter may be adjusted manually or autonomously to align oneor more boresights with one or more light sources. At 1936, calibrationmay be evaluated by, for example, detecting light beams passing througheach boresight. If each boresight is detected to allow light to passthrough its interior, then an emitter is calibrated. Otherwise, flow1900 continues back to 1934 to perform a next calibration operation.

Referring back to 1904, if a determination indicates multiple camera maybe used, flow 1900 continues to 1960. At 1960, an automated reality(“AR”)-aided calibration camera may be implemented. At 1962, at leasttwo cameras may be synchronized to capture images of a target or otherobjects in synchronicity. For example, an in-line camera and an ARcamera may be synchronized such that, for example, each pixel in animage generated by the AR camera is similar or equivalent to acorresponding pixel in the in-line camera. At 1964, a virtual targetimage may be generated in an image generated by an AR camera, thevirtual target image including pixels associated with an optical sightin another image generated by an in-line camera. At 1966, a laser beamaligned with a direction of an emitter may be generated. At 1968, anemitter (or nozzle) may be adjusted to align an image of a laser beamwith a virtual target image, thereby calibrating an emitter. At 1970,calibration of an emitter may be evaluated, and may be recalibrated ifso determined at 1972. If recalibration is needed, flow 1900 returns to1966. Otherwise, flow 1900 terminates.

FIGS. 20 and 21 are diagrams depicting an example of calibratingtrajectories of agricultural projectiles in-situ, according to someexamples. Diagram 2000 of FIG. 20, which is a rear view of exemplarycalibration components, includes an agricultural projectile deliverysystem 2001 including a motion estimator/localizer 2019 and one or moresensors 2070, including airflow direction sensor 2027 and airflow speedsensor 2029. Diagram 2000 also includes a windage emitter 2017 and anemitter 2013, as well as image capture devices 2041 a and 2041 b.Windage emitter 2017 may be configured to emit a sacrificial or testemission, such as projectile 2011 a, to determine, for example, effectsof abiotic or environmental factors, including effects of a gust of windon a trajectory of emitter 2013. Emitter 2013 may be configured todeliver a treatment to an agricultural target 2022 a at an emission timeat which target 2022 a aligns with a point at optical sight 2026 a. Notethat elements depicted in diagram 2000 of FIG. 20 may include structuresand/or functions as similarly-named elements described in connection toone or more other drawings.

In operation, target 2022 a may be identified as an agricultural objectto which a treatment may be applied via emitter 2013. Sensors 2070 maybe used to identify a non-actionable target, such as a leaf 2023 a, toperform a windage evaluation. Hence, logic in agricultural projectiledelivery system 2001 may classify leaf 2023 a as a windage target 2023a. In some examples, windage emitter 2017 may be configured to emit aninert material, such as water, as projectile 2011 a to evaluate wind asa factor. Camera 2041 a may be used to determine whether water-basedprojectile 2011 a intercepts windage target 2023 a. Based on whetherprojectile 2011 a intercepts windage target 2023 a, a trajectory foremitter 2013 may be modified in-situ (e.g., during application of one ormore treatments) to enhance probabilities that an agriculturalprojectile 2012 a intercepts target 2022 a. Camera 2041 b may be used todetermine whether projectile 2012 a intercepts target 2022 a. Note thatin some cases, windage emitter 2017 may be implemented as anotheremitter 2013 that applies a treatment.

FIG. 21 is a diagram 2100 that includes a top view of exemplarycalibration components, whereby sensors 2027 and 2029 and cameras 2041 aand 2041 b may be implemented to adjust trajectories of emitter 2013 tocounter environmental effects including wind. Note that elementsdepicted in diagram 2100 of FIG. 21 may include structures and/orfunctions as similarly-named elements described in connection to FIG. 20or any other one or more other drawings. In operation, consider anexample in which an original trajectory 2132 of a windage projectile2111 b may be generated by logic of agricultural projectile deliverysystem 2001 to counter wind as sensed by sensors 2027 and 2029. Further,the logic may be configured to track a time to emit windage projectile2111 b. As shown, camera 2014 a may capture imagery depicting windageprojectile 2111 b being deflected onto a deflected trajectory 2133 dueto, for example, wind or other external forces. In response, logic ofagricultural projectile delivery system 2001 may be configured to adjustoriginal trajectory 2137 of emitter 2013 to calculate an adjustedtrajectory 2139 so that an agricultural projectile may be delivered to atarget via a predicted trajectory 2136. In some cases, adjustedtrajectory 2139 may be associated with an adjusted activation time 2126b at which emitter 2013 may propel agricultural projectile 2112 b via apredicted trajectory 2139 so as to intercept target 2022 a as if alignedwith optical sight 2026 a. Note that adjusted activation time 2126 b maybe adjusted from an initial activation time by an amount identified asdifferential activation time 2138. In some alternative examples,payloads 2192 emitted by windage emitter 2017 and emitter 2013 may beassociated with heating/cooling (“H/C”) elements 2190 to apply orextract different amounts of thermal energy. In examples in whichcameras 2041 a and 2041 b are configured to detect infrared light,payloads 2192 may be elevated or cooled to different temperatures forapplication to agricultural objects at night time (e.g., withoutsunlight). Temperature differentials of payloads may be distinguishablefrom each other as well as from infrared light reflected from variousagricultural objects. As such, one or more agricultural treatments maybe applied to agricultural objects at any time of the day regardless ofthe presence of sunlight.

FIG. 22 is a diagram depicting deviations from one or more opticalsights to another one or more optical sights, according to someexamples. Diagram 2200 includes an image capture device 2204 configuredto generate an agricultural environment image 2201 b based onagricultural environment 2201 a. Diagram 2200 also includes anagricultural treatment delivery vehicle 2219 with a ground-mappingsonar/radar sensor unit 2270 and a trajectory processor 2283 of anagricultural treatment delivery system 1284. At a time, t1, trajectoryprocessor 2283 may be configured to detect a first subset of opticalsights for images of targets 2222 a, 2222 b, and 2222 c, and may befurther configured to track movement of pixels representing images oftargets 2222 a, 2222 b, and 2222 c via, for example, a projectedalignment tracking line, such as line 2223. Here, trajectory processor2283 at time, t1, may be configured to select optical sight 2226 b toalign with target 2222 a, select optical sight 2226 c to align withtarget 2222 b, and select optical sight 2226 d to align with target 2222c.

At time, t2, initial positions of an array of emitters 2291 at time, t1,is changed to another position (e.g., relative to positions of targets2222 a to 2222 c) and is depicted as an array of emitters 2292 at time,t2. For example, one or more sensors (e.g., accelerometers and the like)may detect a change in elevation 2239 as vehicle 2210 traverses unevensoil topology 2290. Responsive to a change in elevation, a second subsetof optical sights may be selected to align with targets 2222 a to 2222c. For example, optical sight 2227 a may be selected to align withtarget 2222 a, optical sight 2227 b may be selected to align with target2222 b, and optical sight 2227 c may be selected to align with target2222 c. Therefore, trajectory processor 2283 may be configured tode-select and select any optical sight as a function of whether anoptical sight is optimal. Ground-mapping sonar/radar sensor unit 2270may be configured to scan a surface of ground topology 2290 to identifyelevations (e.g., bumps) to predict changes in optical sight selection.

FIG. 23 is a diagram depicting an agricultural projectile deliverysystem configured to implement one or more payload sources to providemultiple treatments to one or more agricultural objects, according tosome examples. Diagram 2300 includes an image capture device 2304configured to capture an agricultural environment image 2320 of anagricultural environment 2301, which may include any number of plants(e.g., trees), at least in the example shown. Diagram 2300 also includesan agricultural projectile delivery system 2381 configured to identifymultiple types of agricultural objects via image 2320 in agriculturalenvironment 2301, select an action associated with at least a subset ofdifferent types of agricultural objects, and deliver a specifictreatment to a subset of agricultural objects as a function of, forexample, a type or classification of agricultural object, as well asother factors, including context (e.g., season, stage of growth, etc.).Agricultural projectile delivery system 2381 may be configured toreceive policy data 2372, indexed object data 2374, sensor data 2376,and position data 2378, one or more of which may be implemented asdescribed herein. Further, agricultural projectile delivery system 2381may be configured to select one or more payload sources 2390 (andamounts thereof) to apply as multiple agricultural projectiles eithersequentially or simultaneously. For example, agricultural projectiledelivery system 2381 may be configured to select different payloadsources 2390 to deliver different agricultural projectiles, such asagricultural projectiles 2312 a to 2312 j. As shown, agriculturalprojectile delivery system 2381 may include a target acquisitionprocessor 2382, a trajectory processor 2383, and an emitter propulsionsubsystem 2385, one or more of which may have one or morefunctionalities and/or structures as described herein. Note thatelements depicted in diagram 2300 of FIG. 23 may include structuresand/or functions as similarly-named elements described in connection toone or more other drawings.

In at least one example, target acquisition processor 2382 may includean object identifier 2384, an event detector 2386, an action selector2388 and an emitter selector 2387. In some implementations, functionsand structures of emitter selector 2387 may be disposed in trajectoryprocessor 2383. Object identifier 2384 may be configured to identifyand/or classify agricultural objects detected in agriculturalenvironment image 2320 based on, for example, index object data 2374 andsensor data 2376, among other data. To illustrate operation of objectidentifier 2384, consider that object identifier 2384 may be configuredto detect one or more objects 2322 a to 2329 a, each of which may beclassifiable. For example, object identifier 2384 may detect andclassify object 2322 a as a blossom 2322 b. Object identifier 2384 maydetect and classify object 2321 a as a spur 2321 b, and may detect andclassify object 2323 a as a spur 2323 b. Object identifier 2384 maydetect and classify object 2324 a as a weed 2324 b, and may detect andclassify object 2325 a as a rodent 2325 b. Object identifier 2384 maydetect and classify object 2326 a as a disease 2326 b, such as a fungus.Object identifier 2384 may detect and classify object 2327 a as a pest2327 b, such as a wooly aphid. Object identifier 2384 may detect andclassify object 2328 a as a fruit 2328 b to be applied with anidentifying liquid that operates similar to a biological “bar code” toidentity provenance. And, object identifier 2384 may detect and classifyobject 2329 a as a leaf 2329 b.

One or more of event detector 2386 and action selector 2388 may beconfigured to operate responsive to policy data 2372. Event detector2386 may be configured to identify an event associated with one or moreobjects 2322 a to 2329 a. For example, event detector 2386 may beconfigured to detect an event for blossom 2322 b, whereby associatedevent data may indicate blossom 2322 b is a “king blossom.” Responsiveto an event identifying a king blossom, action selector 2388 may beconfigured to determine an action (e.g., based on policy data 2372),such as applying a treatment that pollinates blossom 2322 b. As anotherexample, consider that event detector 2386 may be configured to detectan event for weed 2324 b, whereby associated event data may indicatethat weed 2324 b has sufficient foliage prior to germination to beoptimally treated with an herbicide. Responsive to generation of dataspecifying that an event identifies a growth stage of a weed, actionselector 2388 may be configured to determine an action (e.g., based onpolicy data 2372), such as applying a treatment that applies anherbicide to weed 2324 b. Event detector 2386 and action selector 2388may be configured to operate similarly for any identified agriculturalobject.

Emitter selector 2387 is configured to identify one or more opticalsights for each subset of a class of agricultural objects (e.g., one ormore optical sights may be associated with agricultural objectsidentified as pests 2327 b). In various examples, one or more groups ofoptical sights may be used to treat multiple types or classes ofagricultural objects. Trajectory processor 2383 may be configured toidentify each subset of optical sights configured for a type or class ofagricultural object and may track identified/classified agriculturalobjects as they move to corresponding optical sights. Upon detectingalignment of a type or class of agricultural object as a target with anoptical sight, emitter propulsion subsystem 2385 may be configured toselect one of payload sources 2390 to apply a specific treatment for atype or class of target that aligns with an associated optical sight.

In various examples, agricultural projectile delivery system 2381 maydeliver customized treatments as agricultural projectiles to one or moretypes or classes of agricultural objects 2322 a to 2329 a, any treatmentmay be performed individually and sequentially, or in combination ofsubsets thereof. To apply a treatment to blossom 2322 b, one or moreagricultural projectiles 2312 a originating from one of payload sources2390 may be applied to blossom 2322 b. To apply a treatment to spur 2321b, one or more agricultural projectiles 2312 b originating from one ofpayload sources 2390 may be applied to spur 2321 b to encourage growth(e.g., one or more agricultural projectiles 2312 b may include a growthhormone). To apply a treatment to spur 2323 b, one or more agriculturalprojectiles 2312 c originating from one of payload sources 2390 may beapplied to spur 2323 b to regulate growth (e.g., one or moreagricultural projectiles 2312 c may include a growth regulator toimplement, for example, chemical pruning). To apply a treatment to weed2324 b, one or more agricultural projectiles 2312 d originating from oneof payload sources 2390 may be applied to weed 2324 b to terminategrowth (e.g., one or more agricultural projectiles 2312 d may include anherbicide).

To apply a treatment to rodent 2325 b, one or more agriculturalprojectiles 2312 e originating from one of payload sources 2390 may beapplied to rodent 2325 b to reduce rodent population (e.g., one or moreagricultural projectiles 2312 e may include a rodenticide to disperserodents, including voles, etc.). To apply a treatment to disease 2326 b,one or more agricultural projectiles 2312 f originating from one ofpayload sources 2390 may be applied to disease 2326 b to reduce adisease (e.g., one or more agricultural projectiles 2312 g may include afungicide to reduce, for example, apple scab fungi). To apply atreatment to pest 2327 b, one or more agricultural projectiles 2312 goriginating from one of payload sources 2390 may be applied to pest 2327b to reduce an infestation of an insect (e.g., one or more agriculturalprojectiles 2312 g may include an insecticide to reduce, for example,wooly aphid populations). To apply a treatment to leaf 2329 b, one ormore agricultural projectiles 2312 h originating from one of payloadsources 2390 may be applied to leaf 2329 b to apply a foliage fertilizeror reduce leaf-related diseases (e.g., one or more agriculturalprojectiles 2312 h may include a fungicide to reduce, for example, peachleaf curl for peach trees). To apply a treatment to fruit 2328 b, one ormore agricultural projectiles 2312 j originating from one of payloadsources 2390 may be applied to fruit 2328 b to apply a biological ormolecular-based tag (e.g., one or more agricultural projectiles 2312 jmay include a synthetic DNA to apply to a crop to identify provenance atvarious degrees of resolution, such as from a portion of an orchard to atree to an agricultural object.).

According to some examples, payload sources 2390 each may be contained avessel that may be configured as a “cartridge,” which may be adapted forefficient connection and re-filling over multiple uses in contest ofemploying autonomous agricultural treatment delivery vehicles as, forexample, a “robotic-agricultural-vehicles-as-a-service.” In someexamples, payload sources 2390 may include any type or amount ofchemistries, any of which may be mixed together in-situ (e.g., duringapplication of treatments), whereby logic in agricultural projectiledelivery system 2381 may be configured to determine ratios, proportions,and components of mixtures, whereby any one of agricultural projectiles2312 a to 2312 j may be composed of a mixture of chemistries (e.g.,derived from two or more payload sources 2390). Mixture of thechemistries may occur as an agricultural treatment delivery vehicletraverses paths when applying treatments. As such, mixing of chemistriesin real-time (or near real-time) provides for “just-in-time” chemistriesfor application to one or more agricultural objects. In some cases,“recipes” for mixing chemistries may be received and update in real timeas a vehicle is traversing paths of an orchard. According to someexamples, payload sources 2390, as cartridges, may be configured toapply an agricultural projectile as an experimental treatment. As such,application of an experimental agricultural projectile may includeapplying an experimental treatment to agricultural objects to implementa test including A/B testing or any other testing technique to determinean efficacy of a treatment.

FIG. 24 is an example of a flow diagram to implement one or more subsetsof emitters to deliver multiple treatments to multiple subsets ofagricultural objects, according to some embodiments. Flow 2400 begins at2402. At 2402, sensor-based data describing an environment may bereceived, the sensor-based data representing agricultural objects for ageographic boundary. For example, as an agricultural projectile deliveryvehicle traverses one or more paths to deliver multiple treatments tomultiple subsets of agricultural objects, sensor data (e.g., image data)may also be captured for later analysis or to facilitate delivery one ormore treatments to one or more agricultural objects.

At 2404, data representing one or more subsets of indexed agriculturalobjects may be received. For example, each subset of indexedagricultural objects may relate to a different type or class ofagricultural object. One subset of indexed agricultural objects mayrelate to a class or type of fruit disease, whereas another subset ofindexed agricultural objects may relate to a class or type of pest.Another subset of indexed objects may relate to a class or type ofstage-of-growth of, for example, a fruit bud.

At 2406, data representing one or more policies may be received. Atleast one policy may be received in association with a subset of indexedagricultural objects, whereby at least one policy may specify one ormore actions or treatments to be performed for a class or type ofagricultural objects.

At 2408, each agricultural object in a subset of agricultural objectsmay be identified. For example, indexed agricultural object data mayinclude identifier data that uniquely relates to a unique agriculturalobject, such as a one cluster of apple buds, whereby the cluster ofapple buds may be distinguishable for any other cluster on the tree, orthroughout an orchard, or other geographic boundary. Or, a determinationto apply a treatment to an agricultural object may be determined in-situabsent policy information for a particular agricultural object. Forexample, an agricultural object may be changed state, which had beenundetected or unpredicted. Agricultural projectile delivery vehicle maydetect the changed state in real time and apply a treatment absent apolicy for that object.

At 2410, an action to be applied may be selected, based on policy data,the action being linked to the agricultural object. At 2412, an emittermay be selected to apply the action. For example, an emitter may beconfigured to deliver one or more units of treatment (e.g., one or moreagricultural projectiles) to an agricultural object. At 2414, adetermination is made whether there is another agricultural object in asubset or class of agricultural objects. If so, flow 2400 moves back to2410. Otherwise, flow 2400 moves to 2416 at which a determination ismade as to whether there is another subset of agricultural objects forwhich a treatment may be applied. If so, flow 2400 moves back to 2410,otherwise flow 2400 moves to 2418. At 2418, various subsets of emittersmay be activated to provide treatment to multiple sets of agriculturalobjects, for example, as an agricultural treatment delivery vehicletraverses over one or more paths adjacent to the multiple subsets ofagricultural objects.

FIG. 25 is an example of a flow diagram to implement one or morecartridges as payload sources to deliver multiple treatments to multiplesubsets of agricultural objects, according to some embodiments.According to various examples, an agricultural treatment delivery systemmay granularly, with micro-precision, monitor agricultural objects overtime (e.g., through stages-of-growth), whereby an agricultural objectmay be a basic unit or feature of a tree (e.g., a leaf, a blossom, abud, a limb, etc.) that may be treated with micro-precision rather than,for example, spraying a plant as a whole. Therefore, implementation ofone or more agricultural treatment delivery vehicles, which may operateautonomously to navigate and apply agricultural treatments, may conserveamounts of chemistries (e.g., amounts of fertilizers, herbicides,insecticides, fungicides, growth hormones, etc.). Further, asagricultural treatment delivery systems may be implemented in a fleet ofautonomous agricultural treatment delivery vehicles, an entity thatprovides “robotic-agricultural-vehicles-as-a-service” may be able toaccess and use a variety of chemistries from a variety of manufacturers,including relatively expensive chemistries under research anddevelopment that are often out of the reach of small and impoverishedfarmers. As such, an entity can distribute costs over a broad user base,thereby enabling smaller farmers and impoverished farmers to accesschemistries they might otherwise may not have access via use of anagricultural treatment delivery vehicle as described herein.

Normatively, agricultural chemicals are available for purchasepredominantly in units of 275 gallons (e.g., in a tote container), 5gallon buckets, or 2.5 gallon jugs, among others. Cost savings by buyingin bulk may be less cost effective if amounts remain used. According tovarious examples, autonomous agricultural treatment delivery vehiclesdescribed herein may implement “cartridges” as payload sources thatfacilitate ease of replacement or refilling (e.g., in-situ). Forexample, an autonomous agricultural treatment delivery vehicles mayautonomously detect insufficient amounts of a chemistry (e.g., based onpolicy data that requires an action to consume that chemistry), and thenmay autonomously refill its payload at refilling stations located on afarm or remotely. Or, cartridges may be shipped to a destination toreplace empty or near-empty cartridges.

In view of the foregoing, flow 2500 begins at 2502. At 2502, action datamay be received, for example, to perform one or more policies. Forexample, action data may be received from a precision agriculturalmanagement platform configured to employ computational resources toanalyze previously-recorded sensor data from autonomous agriculturaltreatment delivery vehicles for purposes of generating policies withwhich to treat numerous agricultural objects in a geographic boundary,such as in an orchard. At 2504, a determination is made as to whetheraction data is received into an autonomous agricultural treatmentdelivery vehicle or an agricultural projectile delivery system (e.g.,with manual navigation) for performing one or more policies associatedwith an orchard or a farm. If yes, flow 2500 moves to 2511. At 2511,action data may be stored in on-board memory as policy data, which maybe configured to specify specifics treatments that are to be applied tospecific agricultural objects, at particular times and/or amounts, or inaccordance with any other parameter.

At 2513, a target acquisition processor may be configured to apply oneor more actions for a subset agricultural objects. For example, thetarget acquisition processor may be configured to identify and enumerateeach agricultural object that is identified as receiving particularaction, and thus may determine an amount of payload that is to bedistributed over a number of agricultural projectiles to treat a numberof agricultural objects. At 2515, computations are performed todetermine whether payload sources (e.g., in cartridges) are sufficientto implement actions over a group of identified agricultural objects. At2517, a determination is made as to whether payload source amount isinsufficient. If not, at least one cartridge may need to be charged(e.g., filled to any level) or replaced at 2519. For example, anautonomous agricultural treatment delivery vehicle may driveautonomously to a refilling station local to, for example, an orchard orfarm. As such, a cartridge may be charged with one of a germinationpayload (e.g., pollen) or a cluster-thinning payload (e.g., ATS/LimeSulfur, or the like). Or, one or more cartridges may be shipped to thatlocation. Regardless, flow 2500 moves to 2531 to optionally generate oneor more maps to navigate at least one or more emitters to apply one ormore actions associated with the group of identified agriculturalobjects. At 2533, an autonomous agricultural treatment delivery vehiclemay be navigated in accordance with the map. At 2535, one or moreemitters may be configured to execute the actions to, for example,deliver treatments to one or more targeted agricultural objects.

Referring back to 2504, if action data is not received into anautonomous agricultural treatment delivery vehicle or an agriculturalprojectile delivery system, then flow 2500 continues to 2506. At 2506, acomputing device is identified that may be configured to provision oneor more cartridges to include one or more payload sources. For example,the computer device may be implemented at a geographic location at whichcartridges may be provisioned at distances relatively close to ageographic boundary, such as a farm or an orchard. At 2508, a subset ofcartridges may be provisioned as a function of one or more policies withwhich to implement the action data. At 2510, a determination is made asto whether a policy ought to be updated. For example, recently receivedsensor data may indicate, for example, a sufficient number of crops haveentered a later stage of growth, which may cause flow 2500 to move to2522 to select payloads types customized to accommodate modifications inpolicies (e.g., changes in payload types to be applied to agriculturalobjects). At 2524, one or more cartridges may be filled, for example,remotely from a geographic boundary (e.g., an orchard) and shipped to adestination via a package-delivering service or via an entity providingan autonomous agricultural treatment delivery vehicle as a service. At2526, one or more cartridges may be transported to the geographicalboundary for which policy data applies. At 2528, action data (i.e.,policy data) may be transmitted to an agricultural projectile deliverysystem for implementation along with cartridges shipped to a location atwhich the agricultural projectile delivery system is located.

FIGS. 26 to 31 are diagrams depicting components of an agriculturaltreatment delivery vehicle configured to sense, monitor, analyze, andtreat one or more agricultural objects of a fruit tree through one ormore stages of growth, according to some examples. FIG. 26 includes oneor more components of an agricultural treatment delivery vehicle 2601,including various vehicle components 2610 (e.g., drivetrain, steeringmechanisms, etc.), a mobility platform 2614, a sensor platform 2613, oneor more payload sources 2612, and an agricultural projectile deliverysystem 2611. Agricultural treatment delivery vehicle 2601 may beconfigured to identify one or more stages of growth for an agriculturalobject, and may be further configured to determine policies describingone or more actions or treatments to apply to various agriculturalobjects all year round, including a life cycle of a fruit crop from budto harvest. Note that elements depicted in diagrams 2600 of FIG. 26through diagram 3100 of FIG. 31 may include structures and/or functionsas similarly-named elements described in connection to one or more otherdrawings or as otherwise described herein. Note, too, while FIGS. 26 to31 may refer to stages of growth for an apple crop, any one or more ofthe functions described herein may be applicable to other fruit trees,nut trees, or any other vegetation or plant, including vegetable crops(e.g., row crops, ground crops, etc.) and ornamental plants.

In some examples, one or more policies may include various actions toprovide various treatments to agricultural objects depicted in diagrams2600 to 3100. For example, one or more policies may include dataconfigured to manage apple crops with an aim to “save the king” (i.e.,save a king bloom). One or more policies may be implemented over one ormore stages of growth of an apple-related agricultural object.Agricultural projectile delivery system 2611 may be configured to applyone or more treatments to an agricultural object, such as a bud orblossom, with micro-precision by, for example, delivering a treatment asan agricultural projectile. Thus, agricultural projectile deliverysystem 2611 may treat portions of an apple tree on at least aper-cluster basis as well as a per-blossom basis, according to variousexamples. One or more policies may be configured to perform an action toisolate a king blossom on each cluster, and to perform another action totrack one or more clusters (e.g., at an open cluster stage of growth) todetect, via sensor platform 2613, whether a king blossom (as anagricultural object) has “popped.” Also, a policy may also track whetherany lateral blossoms (as agricultural objects) have remained closed.Another policy may include performing an action to germinate a kingblossom and to terminate neighboring lateral blossoms of a commoncluster. Thus, lateral blossom may be autonomously terminated ratherthan being mechanically (e.g., manually by hand) terminated. In variousexamples, one or more policies configured to “save the king” mayfacilitate enhanced crop yields. For example, performing actions andtreatments with micro-precision facilitates optimizing attributes of anapple, such as color, size, etc. Thus, agricultural projectile deliverysystem 2611 may assist in managing apple crops with micro-precision toenhance yields of apples that are sized optimally, for example, forpacking. In some examples, about 88 apples per box may be obtained(e.g., rather than 100 apples per box). Also, terminating lateralblossom in accordance with functions and/or structures described hereinfacilitates increased amount of nutrients a fruit tree may supply toremaining blossoms to help produce larger, healthier fruit. A fewpolicies may be implement to “thin a cluster,” thereby terminating eachbud or blossom associated with a particular cluster. Hence, the variousfunctions and/or structures described herein may enhance fruitproduction while reducing costs of labor.

Diagram 2600 depicts a portion of a limb, for example, in late winter orearly spring (e.g., in the northern hemisphere) during a “dormant” stageof growth. As shown, the limb may include fruit buds 2621 a, leaf buds2621 c, one or more spurs 2621 b, and one or more shoots 2621 d. Alsoshown is a fruit bud 2622 in a dormant state. One or more policies maycause agricultural projectile delivery system 2611 to inspect one ormore portions of a limb to determine whether a treatment may be applied.For example, a foliar growth hormone may be applied as one or moreagricultural projectiles to a spur to encourage growth. An example of afoliar growth hormone includes gibberellic acid, or gibberellin, or thelike. By contrast, one or more policies may cause agriculturalprojectile delivery system 2611 to inspect a portion of a limb todetermine whether “chemical pruning” may be implemented by applying agrowth regulator (e.g., paclobutrazol or the like) as one or moreagricultural projectiles.

Diagram 2700 depicts one or more buds 2722 (as agricultural objects)transitioning to a next stage of growth, such as a “half-inch” green2724 (as an agricultural object). One or more policies may be configuredto direct agricultural projectile delivery system 2611 to inspect andtrack development of buds 2722 and “half-inch” greens 2724, and, ifavailable, apply a treatment.

Diagram 2800 depicts one or more “half-inch” greens for FIG. 27transitioning to next stages of growth, such as a “tight cluster” 2826(as an agricultural object), or a “full/pink cluster 2827 (as anagricultural object). Full/pink cluster 2827 may also be referred to asan open cluster. One or more policies may be configured to causeagricultural projectile delivery system 2611 to inspect and trackdevelopment of agricultural objects 2826 and 2827, and, if available,apply a treatment. For example, a determination may be made that tightcluster 2826 may be growing slower than as expected. As such, a policymay cause agricultural projectile delivery system 2611 to apply a growthhormone, with micro-precision, to tight cluster 2826 to promote growth.

Diagram 2900 depicts one or more agricultural objects 2826 and 2827 ofFIG. 28 transitioning to a next stage of growth. For example, afull/pink cluster 2927 may transition into a “king blossom” stage inwhich a king blossom 2928 (e.g., a first blossom) opens. In variousexamples, agricultural projectile delivery system 2611 may be configuredto apply a treatment with micro-precision to center 2928 b within aperimeter 2928 a of king blossom 2928. For example, a policy may causeagricultural projectile delivery system 2611 to apply a treatment tocenter 2928 b by, for example, emitting an agricultural projectile tointercept center 2928 b to germinate the blossom. In some cases, two ormore king blossoms may be germinated and saved.

Diagram 3000 depicts one or more agricultural objects 2928 of FIG. 29transitioning to a next stage of growth. For example, a king blossom2928 may transition into a “lateral” stage in which lateral blossoms3029 open about king blossom 3028. In various examples, agriculturalprojectile delivery system 2611 may be configured to apply a treatmentwith micro-precision to lateral blossoms 3029 (e.g., to the centers orportions thereof). For example, a policy may cause agriculturalprojectile delivery system 2611 to apply a treatment (e.g., a causticchemical) to lateral blossoms 3029 to terminate growth of the lateralblossoms, thereby “saving the king.” Alternatively, some policies maycause agricultural projectile delivery system 2611 to apply a caustictreatment to both lateral blossoms 3029 and a king blossom 3028, therebythinning an entire cluster.

Diagram 3100 depicts one or more agricultural objects 3028 and 3029 ofFIG. 30 transitioning to next stages of growth. For example, lateralblossoms 3029 and king blossom 3028 may transition into a “fruit set” or“pedal fall” stage (as an agricultural object) in which petal havefallen. Also, king blossom 3028 of FIG. 30 may transition to a “fruit”stage of growth in which a fruit 3130 develops and ripens. Agriculturalprojectile delivery system 2611 may emit an agricultural projectile toapply a synthetic DNA to fruit 3130 to identify its origins later in thefood production process. Note that other policies, such as applyingherbicides, insecticides, fungicides, and the like, may be implementedat one or more of the stages of growth described in FIGS. 26 to 31.

FIG. 32 is a diagram depicting an example of a flow to manage stages ofgrowth of a crop, according to some examples. Flow 3200 starts at 3202.At 3202, an agricultural projectile delivery system may navigateautonomously to inspect, monitor, and treat one or more agriculturalobjects. At 3204, sensors may be implemented to capture datarepresenting agricultural objects. At 3205, a predictive state of anagricultural object may be predicted, such as at a precisionagricultural management platform, according to some examples. At 3206,policy data configured to perform one or more actions for one or moreagricultural objects may be accessed. At 3208, a determination is madeas to whether an action is associated with a pre-blossom stage. If so,flow 3200 moves to 3221 to apply a first subset of actions, such asapplying growth hormone to a spur to promote limb growth. Otherwise,flow 3200 moves to 3210, at which a determination is made as to whetheran associated action relates to a blossom stage. If not, flow 3200 movesto 3232. But if so, flow 3200 moves to 3223 to identify a blossom as“king” of a cluster. At 3225, a second subset of actions may beperformed, including germinating a blossom. Flow 3200 then moves to3227, at which a determination is made as to whether lateral blossomsare identified. If so, flow 3200 moves to 3229 to perform another actionin the second subset of action, such as killing the lateral blossoms.Flow 3200 then moves to 3232, at which a determination is made as towhether an action applies to a post-blossom stage. If so, flow 3200moves to 3241 to perform a third subset of actions, such as applying afungicide to a fruit exhibiting “apple scab.” Flow 3200 then moves 3234,at which a determination is made as to whether a harvest is complete. Ifnot, flow 3200 moves to 3202, otherwise flow 3200 terminates. One ormore of the above regarding flow 3200 may be implemented using anagricultural projectile delivery system, which may include one or moreprocessors and one or more applications or executable instructionsstored in memory.

FIG. 33 is a diagram depicting an agricultural projectile deliveryvehicle implementing an obscurant emitter, according to some examples.Diagram 3300 includes an agricultural projectile delivery vehicle 3310including an imaging device 3312 (e.g., a camera) and an optionalillumination device 3314, which may be omitted. Further, agriculturalprojectile delivery vehicle 3310 also may include an obscurant emitter3321 c that is configured to generate an obscurant wall 3320 interposedbetween, for example, a source of backlight, such as sun 3302, and anagricultural object 3399. As agricultural projectile delivery vehicle3310 traverses a path adjacent a crop, such as a fruited tree, datagenerated by imaging sensors may be degraded when trying to capture animage of object 3399 that is disposed in between a bright source ofbacklight, such as sun 3302, and camera 3312. Generation of obscurantwall 3320 may facilitate an increase of a dynamic range for imagecapture device 3312 (e.g., enhancing a ratio between a largest value anda smallest value of luminous intensity). Obscurant wall 3320 forms adynamic (e.g., temporary) enclosure as a light barrier to reduce anamount of light from backlight source 3302 relative to the agriculturalobject 3399. In some examples, obscurant emitter 3321 c may beimplemented as a mist generator configured to generate portions 3332and/or 3334 of mist or water vapor using, for example, an ultrasonicgenerator or transducers. Ultrasonic transducers may be configured toconvert liquid water into a mist of the one or more clouds of waterdroplets, which may be viewed as “eco-friendly.”

In operation, a light intensity sensor (not shown) may be configured todetect a value of luminous intensity originating, for example, frombacklight source 3302. If a value of luminous intensity exceeds athreshold value, obscurant emitter 3321 c may be configured to generateobscurant wall 3320 in, for example, a region between a medial line 3305and backlight source 3302. The obscurant may be directed that regionusing, for example, one or more blowers 3322 c or directional fans.Portions of mist or fog provides a dynamic enclosure that may not havedrawbacks of physical enclosures, such a shrouds, that are typicallyadapted for a specific row crop. Such a dynamic enclosure may adapt todifferently-sized trees or crops. Further, by reducing backlight,obscurant wall may obviate a need to synchronize a camera sensor (e.g.,a camera shutter synchronized with a flash) or perform additional imageprocessing involving, for example, using multiple exposures or tonemapping algorithms. In some examples, one or more obscurant emitters3321 a and 3321 b and one or more blowers 3322 a and 3322 b may bedisposed on an encompassing structure 3325, which may be omitted.

FIG. 34 is a diagram depicting an example of a flow to facilitateimaging a crop in an environment with backlight, according to someexamples. In some examples, flow 3400 enhances a dynamic range ofcaptured images of agricultural objects with environments withbacklight, such as sunlight or moonlight (e.g., a full moon). At 3402,location and/or sensor data of an environment including an agriculturalobject may be received. At 3404, an agricultural object may beidentified based on the location and/or sensor data received at 3402. At3406, a determination is made as to whether an identified agriculturalobject may be correlated to index data. If so, flow 3400 moves to 3408,at which a spatial location of an agricultural object may be determined.At 3410, an identified agricultural object may be correlated to indexobject data, thereby confirming that sensor data (e.g., image data)being received at a sensor is identifying an agricultural object that isthe same in the indexed data. At 3412, an action may be associated withthe indexed object data. That is, a policy to perform an action (e.g., atreatment) may be associated with indexed object data. At 3414, anagricultural object may be identified as a target to, for example,perform an action. At 3416, determination is made as to whether a valueof backlight as above a threshold value. For example, if an intensity oflight is above a threshold value, and that light originates behind theidentified target, then flow 3400 moves to 3418 to generate anobscurant, such as generating water vapor using ultrasonic generator. At3420, an obscurant may be emitted at a location relative to the targetedagricultural object, the obscurant being disposed between a source ofbacklight and a target agricultural object. At 3422, an image of theagricultural object may be captured.

FIG. 35 is a diagram depicting a pixel projectile delivery systemconfigured to replicate an image on a surface using pixel projectiles,according to some embodiments. Diagram 3500 includes a pixel projectiledelivery system 3511, which may include any number of pixel emitters3542 a, and a mobile computing device 3590, which may include aprocessor configured to execute an application that may provide inputs(e.g., control data) to pixel projectile delivery system 3511. Invarious examples, pixel projectile delivery system 3511 may beconfigured to emit subsets of pixel projectiles 3512 to “paint” orreplicate portions of an image, such as image 3560, upon a surface 3502.In some examples, an application executing on mobile computing device3590 may identify an image 3560 to be replicated on surface 3502, andmay further be configured to determine a reference with which to aligninputs associated with mobile computing device 3590 and correspondingoutputs associated with a replicated image on surface 3502. As shown, areference 3515 a of image 3560 is aligned with reference 3515 b of theimage in the user interface of mobile computing device 3590, which, inturn, may establish a reference 3515 c associated with surface 3502.Therefore, inputs into the user interface of mobile computing device3590 may be correlated to reference 3515 b, and, similarly, outputsemitted out of emitters 3542 a (and impacted points on surface 3502) maybe correlated to reference 3515 c.

To illustrate operation of pixel projectile delivery system 3511,consider that pixel projectile delivery system 3511 may be configured toreceive data 3578 representing image 3560. At least one portion 3515 aof image 3560 may be a reference 3515 a to align with a surfacereference 3515 c associated with surface 3502. Pixel projectile deliverysystem 3511 may be configured to establish electronic communication withmobile computing device 3590, which may be configured to transmitcontrol data 3578 as a function of one or more spatial translations asinputs, whereby one or more spatial translations simulate replication onsurface 3502. Examples of one or more spatial translations are depictedas spatial transitions 3520 a, 3521 a, 3522 a, 3523 a, and 3524 a. Insome cases, each of spatial transitions 3520 a, 3521 a, 3522 a, 3523 a,and 3524 a may be referred to as a unit of spatial translation (e.g., aunit be determined by, for example, a momentary pause or delay inapplying an input).

Pixel projectile delivery system 3511 may be configured to receive datarepresenting a unit of spatial translation, such as one of units ofspatial translation 3520 a, 3521 a, 3522 a, 3523 a, and 3524 a, wherebythe unit of spatial translation may specify a translation relative to areference associated with mobile computing device 3590. In one example,spatial translations may be determined based on translations of, forexample, a simulated targeting sight 3592 that may produce each ofspatial transitions 3520 a, 3521 a, 3522 a, 3523 a, and 3524 a relativeto reference 3515 b, the translations of simulated targeting sight 3592being caused by input into a touch-sensitive graphics user interface. Inanother example, spatial translations may be determined based ontranslations of, for example, motion in two-dimensional space that mayproduce each of spatial transitions 3520 a, 3521 a, 3522 a, 3523 a, and3524 a relative to reference 3515 d. Thus, moving mobile computingdevice 3590 (e.g., within an X-Y plane) may produce spatial translations3520 a, 3521 a, 3522 a, 3523 a, and 3524 a relative to reference 3515 d,whereby one or more motion sensors or accelerometers in mobile computingdevice 3590 generates inputs representing the spatial translations sentvia control data 3578.

Further, pixel projectile delivery system 3511 may be configured todetermine one or more portions 3520 c, 3521 c, 3522 c, 3523 c, 3524 c ofimage 3560 respectively associated with each unit of spatial translation3520 b, 3521 b, 3522 b, 3523 b, and 3524 b relative to reference 3515 c.Note that pixel projectile delivery system 3511 may be configured torespectively map spatial transitions 3520 a, 3521 a, 3522 a, 3523 a, and3524 a relative to reference 3515 d to spatial translation 3520 b, 3521b, 3522 b, 3523 b, and 3524 b relative to reference 3515 c.

Pixel projectile delivery system 3511 may be configured to identify oneor more subsets of pixels (e.g., one or more portions 3520 c, 3521 c,3522 c, 3523 c, 3524 c of image 3560) to be formed on surface 3502responsive to detecting a unit of spatial translation. And, pixelprojectile delivery system 3511 may be configured to cause emission ofone or more subsets of pixel projectiles 3512 directed to impact one ormore portions of surface to form one or more subset of pixels 3520 d,3521 d, 3522 d, 3523 d, and 3524 d relative to surface reference 3515 cto form a replica 3550 b of a portion 3550 a of image 3560.

FIG. 36 is a diagram depicting an example of a pixel projectile deliverysystem, according to some examples. Pixel projectile delivery system3611 may include a target acquisition processor 3682, which may includean object identifier 3684. Pixel projectile delivery system 3611 mayalso include an emitter selector 3687, a trajectory processor 3683, andan emitter propulsion subsystem 3685. Note that elements depicted indiagram 3600 may include structures and/or functions as similarly-namedelements described in connection to one or more other drawings or asotherwise described herein, regardless of whether an implementationnon-agricultural.

Target acquisition processor 3682 may be configured to receive datarepresenting pixel inputs to be replicated on a surface. Objectidentifier 3684 may be configured to detect an image object, such as areference with which to replicate an image. Emitter selector 3687 may beconfigured to select a subset of emitters responsive to inputs selectinga subset of pixels to be replicated. Trajectory processor 3683 may beconfigured to coordinate and manage emission of pixel projectiles, andmay further be configured to generate activation signals to causeemission propulsion subsystem 3685 to propel pixel projectiles to impacta surface relative to a reference.

In some cases, a pixel emitter 3642 a may include, or may be associatedwith, one or more pigment sources, such as pigment source 3644 a,pigment source 3644 b, and pigment source 3644 n, where pigment sourcesmay include RED, GREEN, and BLUE pigments, or may include CYAN, MAGENTA,and YELLOW, or any other pigment combination. Trajectory 3683 may beconfigured to control amounts of pigments into chamber 3643 for propercolor mixing. When activated, emitter propulsion subsystem 3685 maytrigger chamber 3643 to propel pixel projectile 3612 from aperture 3641.In some cases, an input 3647 is configured to push out (e.g., blow out)any remaining pigment out through output 3645 so that chamber 3643 maybe used to emit other pixel projectiles of different colors. Note thatthe above is one example and other implements may be used to replicatean image using a pixel projectile delivery system, according to variousexamples.

FIG. 37 is a diagram depicting an example of a flow to implement a pixelprojectile delivery system, according to some examples. At 3702, datarepresenting at least one portion of an image may be received. Theportion of the image may be configured to provide a reference with whichto align with a surface reference, which may be associated with asurface. Alignment of a reference of an image and a reference on asurface may facilitate synchronicity between input portions of an imageto be replicated or “painted” and outputs of a pixel projectile deliverysystem to “paint” or emit pixel projectiles to impact a surface relativeto a surface reference.

At 3704, electronic communication with a computing device configured totransmit data representing simulation of an application may beestablished. For example, a mobile computing device (e.g., smart phone)may generate inputs describing which portions of an image are to bereplicated on a surface, the communication being established between amobile computing device and a pixel projectile delivery system.

At 3706, data representing a unit of spatial translation specifying atranslation relative to a reference may be received, for example, into apixel projectile delivery system. At 3708, one or more portions of animage associated with a unit of spatial translation relative to areference may be detected. The unit of spatial translation may beconsidered an input to cause replication at a surface. At 3710, a subsetof pixels to be formed or replicated on a surface may be identified. At3712, emission of a subset of pixel projectiles may be caused,responsive to an input. The subset of pixel projectiles may be directedto impact a portion of a surface to form a replica of a portion of theimage

FIG. 38 illustrates examples of various computing platforms configuredto provide various functionalities to components of an autonomousagricultural treatment delivery vehicle and fleet service, according tovarious embodiments. In some examples, computing platform 3800 may beused to implement computer programs, applications, methods, processes,algorithms, or other software to perform the above-described techniques.

In some cases, computing platform 3800 can be disposed in any device,such as a computing device 3890 a, which may be disposed in anautonomous agricultural treatment delivery vehicle 3891, and/or mobilecomputing device 3890 b.

Computing platform 3800 includes a bus 3802 or other communicationmechanism for communicating information, which interconnects subsystemsand devices, such as processor 3804, system memory 3806 (e.g., RAM,etc.), storage device 3808 (e.g., ROM, etc.), an in-memory cache (whichmay be implemented in RAM 3806 or other portions of computing platform3800), a communication interface 3813 (e.g., an Ethernet or wirelesscontroller, a Bluetooth controller, NFC logic, etc.) to facilitatecommunications via a port on communication link 3821 to communicate, forexample, with a computing device, including mobile computing and/orcommunication devices with processors. Processor 3804 can be implementedwith one or more graphics processing units (“GPUs”), with one or morecentral processing units (“CPUs”), such as those manufactured by Intel®Corporation, or one or more virtual processors, as well as anycombination of CPUs and virtual processors. Computing platform 3800exchanges data representing inputs and outputs via input-and-outputdevices 3801, including, but not limited to, keyboards, mice, audioinputs (e.g., speech-to-text devices), user interfaces, displays,monitors, cursors, touch-sensitive displays, LCD or LED displays, andother I/O-related devices.

According to some examples, computing platform 3800 performs specificoperations by processor 3804 executing one or more sequences of one ormore instructions stored in system memory 3806, and computing platform3800 can be implemented in a client-server arrangement, peer-to-peerarrangement, or as any mobile computing device, including smart phonesand the like. Such instructions or data may be read into system memory3806 from another computer readable medium, such as storage device 3808.In some examples, hard-wired circuitry may be used in place of or incombination with software instructions for implementation. Instructionsmay be embedded in software or firmware. The term “computer readablemedium” refers to any tangible medium that participates in providinginstructions to processor 3804 for execution. Such a medium may takemany forms, including but not limited to, non-volatile media andvolatile media. Non-volatile media includes, for example, optical ormagnetic disks and the like. Volatile media includes dynamic memory,such as system memory 3806.

Common forms of computer readable media includes, for example, floppydisk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, or any other mediumfrom which a computer can read. Instructions may further be transmittedor received using a transmission medium. The term “transmission medium”may include any tangible or intangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machine,and includes digital or analog communications signals or otherintangible medium to facilitate communication of such instructions.Transmission media includes coaxial cables, copper wire, and fiberoptics, including wires that comprise bus 3802 for transmitting acomputer data signal.

In some examples, execution of the sequences of instructions may beperformed by computing platform 3800. According to some examples,computing platform 3800 can be coupled by communication link 3821 (e.g.,a wired network, such as LAN, PSTN, or any wireless network, includingWiFi of various standards and protocols, Bluetooth®, NFC, Zig-Bee, etc.)to any other processor to perform the sequence of instructions incoordination with (or asynchronous to) one another. Computing platform3800 may transmit and receive messages, data, and instructions,including program code (e.g., application code) through communicationlink 3821 and communication interface 3813. Received program code may beexecuted by processor 3804 as it is received, and/or stored in memory3806 or other non-volatile storage for later execution.

In the example shown, system memory 3806 can include various modulesthat include executable instructions to implement functionalitiesdescribed herein. System memory 3806 may include an operating system(“O/S”) 3832, as well as an application 3836 and/or logic module(s)3859. In the example shown in FIG. 38, system memory 3806 includes amobility controller module 3850 and/or its components as well as anagricultural projectile delivery controller module 3851, any of which,or one or more portions of which, can be configured to facilitate anautonomous agricultural treatment delivery vehicle and fleet of servicesby implementing one or more functions described herein.

The structures and/or functions of any of the above-described featurescan be implemented in software, hardware, firmware, circuitry, or acombination thereof. Note that the structures and constituent elementsabove, as well as their functionality, may be aggregated with one ormore other structures or elements. Alternatively, the elements and theirfunctionality may be subdivided into constituent sub-elements, if any.As software, the above-described techniques may be implemented usingvarious types of programming or formatting languages, frameworks,syntax, applications, protocols, objects, or techniques. As hardwareand/or firmware, the above-described techniques may be implemented usingvarious types of programming or integrated circuit design languages,including hardware description languages, such as any register transferlanguage (“RTL”) configured to design field-programmable gate arrays(“FPGAs”), application-specific integrated circuits (“ASICs”), or anyother type of integrated circuit. According to some embodiments, theterm “module” can refer, for example, to an algorithm or a portionthereof, and/or logic implemented in either hardware circuitry orsoftware, or a combination thereof. These can be varied and are notlimited to the examples or descriptions provided.

In some embodiments, modules 3850 and 3851 of FIG. 38, or one or more oftheir components, or any process or device described herein, can be incommunication (e.g., wired or wirelessly) with a mobile device, such asa mobile phone or computing device, or can be disposed therein.

In some cases, a mobile device, or any networked computing device (notshown) in communication with one or more modules 3850 and 3851, or oneor more of their components (or any process or device described herein),can provide at least some of the structures and/or functions of any ofthe features described herein. As depicted in the above-describedfigures, the structures and/or functions of any of the above-describedfeatures can be implemented in software, hardware, firmware, circuitry,or any combination thereof. Note that the structures and constituentelements above, as well as their functionality, may be aggregated orcombined with one or more other structures or elements. Alternatively,the elements and their functionality may be subdivided into constituentsub-elements, if any. As software, at least some of the above-describedtechniques may be implemented using various types of programming orformatting languages, frameworks, syntax, applications, protocols,objects, or techniques. For example, at least one of the elementsdepicted in any of the figures can represent one or more algorithms. Or,at least one of the elements can represent a portion of logic includinga portion of hardware configured to provide constituent structuresand/or functionalities.

As hardware and/or firmware, the above-described structures andtechniques can be implemented using various types of programming orintegrated circuit design languages, including hardware descriptionlanguages, such as any register transfer language (“RTL”) configured todesign field-programmable gate arrays (“FPGAs”), application-specificintegrated circuits (“ASICs”), multi-chip modules, or any other type ofintegrated circuit.

According to some embodiments, the term “circuit” can refer, forexample, to any system including a number of components through whichcurrent flows to perform one or more functions, the components includingdiscrete and complex components. Examples of discrete components includetransistors, resistors, capacitors, inductors, diodes, and the like, andexamples of complex components include memory, processors, analogcircuits, digital circuits, and the like, including field-programmablegate arrays (“FPGAs”), application-specific integrated circuits(“ASICs”). Therefore, a circuit can include a system of electroniccomponents and logic components (e.g., logic configured to executeinstructions, such that a group of executable instructions of analgorithm, for example, and, thus, is a component of a circuit).According to some embodiments, the term “module” can refer, for example,to an algorithm or a portion thereof, and/or logic implemented in eitherhardware circuitry or software, or a combination thereof (i.e., a modulecan be implemented as a circuit). In some embodiments, algorithms and/orthe memory in which the algorithms are stored are “components” of acircuit. Thus, the term “circuit” can also refer, for example, to asystem of components, including algorithms. These can be varied and arenot limited to the examples or descriptions provided.

Although the foregoing examples have been described in some detail forpurposes of clarity of understanding, the above-described inventivetechniques are not limited to the details provided. There are manyalternative ways of implementing the above-described inventiontechniques. The disclosed examples are illustrative and not restrictive.

What is claimed:
 1. A method comprising: receiving data to identify anagricultural object with which to capture sensed image data at an imagecapture device; determining a spatial location of the agriculturalobject; calculating an amount of light originating from a light source,the light being sensed at a location in which the spatial location forthe agricultural object is interposed between the light source and theimage capture device; causing emission of an obscurant; and directingthe obscurant to a region interposed between the light source and theagricultural object.
 2. The method of claim 1, further comprising:receiving data representing a location of an agricultural object in theenvironment in which an agricultural projectile delivery vehicletraverses.
 3. The method of claim 2, wherein receiving the datarepresenting the location of the agricultural object to which theagricultural projectile delivery vehicle traverses autonomously.
 4. Themethod of claim 1, wherein causing emission of the obscurant comprises:causing an increase of a dynamic range for the image capture device. 5.The method of claim 1, wherein calculating the amount of lightcomprises: determining a value of luminous intensity.
 6. The method ofclaim 5, further comprising: detecting the value of luminous intensity;and initiating generation of the obscurant.
 7. The method of claim 1,wherein causing emission of the obscurant comprises: forming a dynamicenclosure as a light barrier to reduce the amount of light as abacklight relative to the agricultural object.
 8. The method of claim 1,wherein causing emission of the obscurant comprises: forming one or moreclouds of suspended particulate.
 9. The method of claim 1, whereincausing emission of the obscurant comprises: generating one or moreclouds of water droplets.
 10. The method of claim 9, wherein generatingthe one or more clouds of water droplets comprises: activating one ormore ultrasonic transducers configured to convert liquid water into amist of the one or more clouds of water droplets.
 11. The method ofclaim 1, wherein directing the obscurant to the region comprises:activating a blower.
 12. The method of claim 11, wherein activating theblower comprises: activating a directional fan.
 13. A system comprising:a memory including executable instructions; and a processor, responsiveto executing the instructions, is configured to: receive data toidentify an agricultural object with which to capture sensed image dataat an image capture device; determine a spatial location of theagricultural object; calculate an amount of light originating from alight source, the light being sensed at a location in which the spatiallocation for the agricultural object is interposed between the lightsource and the image capture device; cause emission of an obscurant; anddirect the obscurant to a region interposed between the light source andthe agricultural object.
 14. The system of claim 13 further comprising:an obscurant emitter, one or more blowers, and one or more image capturedevices, any of which may include including one or more of the memoryand the processor.
 15. The system of claim 14 wherein one or moreblowers comprise: one or more directional fans.
 16. The system of claim13 wherein a subset of the instructions to cause emission of theobscurant further causes the processor to: cause an increase of adynamic range for the image capture device.
 17. The system of claim 13wherein a subset of the instructions to calculate the amount of lightcauses the processor to: determine a value of intensity; detect thevalue of intensity; and initiate generation of the obscurant responsiveto detection of the value of intensity.
 18. The system of claim 13wherein a first subset of the instructions to cause emission of theobscurant further causes the processor to: cause an increase of adynamic range for the image capture device.
 19. The system of claim 13,wherein a second subset of the instructions to cause emission of theobscurant further causes the processor to: form a dynamic enclosure as alight barrier to reduce the amount of light as a backlight relative tothe agricultural object.
 20. The system of claim 13, further comprisingone or more ultrasonic transducers configured, responsive to theprocessor, to: convert liquid water into a mist of the one or moreclouds of water droplets to form the obscurant.